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, potctl uses default.

remote-controlplane.yaml

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

potctl 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: datasance.com/v3
kind: KubernetesControlPlane
metadata:
name: albatros
spec:
iofogUser:
  email: [email protected]
  password: h9g84q
config: ~/.kube/config

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

Connect without a YAML file:

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

Add SSH details manually with configure:

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

Disconnect From Edge Compute Network

potctl disconnect

Next steps?

• YAML kinds reference.

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

Edit this page on GitHub!