Skip to main content
Version: v3.9.0

Attach and detach

You can transfer an Edgelet node from one ECN to another by detaching it and attaching it elsewhere.

Detach stops workloads

Detaching an Edgelet node deprovisions it on the Controller. Microservices on that node are shut down. Detach does not uninstall Edgelet from the host.

Detach from the current namespace:

potctl detach agent zebra-1 -n factory-a

If microservices still run on the node, the command fails unless you pass --force.

List detached resources:

potctl get all --detached

Attach to another namespace or ECN:

potctl attach agent zebra-1 -n factory-b

Attach expects Edgelet to still be installed on the host from before detach. It pushes AgentConfig, runs provision, and restores the namespace cache. If the host was wiped, run deploy -f with a fresh Agent manifest instead.

Move between namespaces in one step:

potctl move agent zebra-1 factory-b -n factory-a

This runs detach agent in the source namespace (honors --force when passed) then attach agent in the destination namespace.

Delete vs detach​

CommandControllerHost
detach agentDeletes agent record; saves spec in detached storeDeprovision only; binaries remain
delete agentDeletes agent recordDeprovision + uninstall (uninstall.sh, optional data removal)

Use delete agent when the node should leave the fleet and the host should be cleaned up.

potctl delete agent zebra-1 -n factory-a

Unless --force is set, delete refuses when microservices are still scheduled on the node. --force skips that check.

If SSH details are missing from namespace config, delete skips deprovision and uninstall with a notify message. Restore SSH with configure agent, then retry delete.

System agents on control plane hosts are removed via control plane delete, not ordinary delete agent on reserved system names.

Configure SSH only​

configure agent updates ssh.user, ssh.keyFile, and ssh.port in namespace or detached config. It does not change AgentConfig on the Controller.

potctl configure agent zebra-1 --user ubuntu --key ~/.ssh/new_key --port 22

Use deploy -f with AgentConfig (or agent spec.config) for runtime limits, router, NATS, and EdgeGuard settings.

See also​

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