Connecting To Existing Edge Compute Networks

Connect to an existing ECN instead of deploying a new one.

Use an empty or non-existent namespace for connect. Each cluster should live in its own namespace. When you omit -n, iofogctl uses default.

remote-controlplane.yaml

apiVersion: iofog.org/v3
kind: ControlPlane
metadata:
  name: albatros
spec:
  iofogUser:
    email: [email protected]
    password: h9g84q
  controllers:
  - name: alpaca-1
    host: 30.40.50.1

iofogctl connect -f /tmp/remote-controlplane.yaml

For Kubernetes Control Planes, the --namespace flag must match the Kubernetes namespace where the Control Plane runs.

k8s-controlplane.yaml

apiVersion: iofog.org/v3
kind: KubernetesControlPlane
metadata:
  name: albatros
spec:
  iofogUser:
    email: [email protected]
    password: h9g84q
  config: ~/.kube/config

iofogctl connect -f /tmp/k8s-controlplane.yaml

Connect without a YAML file:

iofogctl connect --ecn-addr 40.50.60.70 --name albatros --email [email protected] --pass h9g84q
iofogctl connect --kube ~/.kube/config --email [email protected] --pass h9g84q

Add SSH details manually with configure:

iofogctl configure controlplane --kube KUBECONFIG
iofogctl configure controller NAME --user USER --key KEYFILE --port PORTNUM
iofogctl configure agent NAME --user USER --key KEYFILE --port PORTNUM
iofogctl configure current-namespace NAMESPACE
iofogctl configure controllers --user USER --key KEYFILE --port PORTNUM
iofogctl configure agents --user USER --key KEYFILE --port PORTNUM

Disconnect From Edge Compute Network

iofogctl disconnect

Next steps?

• YAML kinds reference.

See anything wrong with the document? Help us improve it!

Edit this page on GitHub!