- Documentation
Volcengine Kubernetes Engine
Volcengine Kubernetes Engine
FAQs
Cluster FAQ
Registered cluster FAQ
How do I handle the disconnection of an agent-registered cluster caused by a missing agent?
Registered cluster FAQ
How do I handle the disconnection of an agent-registered cluster caused by a missing agent?
How do I handle the disconnection of an agent-registered cluster caused by a missing agent?
Issue description
A cluster that is registered through an agent remains in a disconnected status for a long period of time.
Cause analysis
When you register a cluster by using an agent, you need to install the agent for communication on an existing node in the cluster. If the agent cannot be installed, the registered cluster will become disconnected in VKE. The following scenarios may occur:
- Scenario 1: If the node to which the Agent belongs is taken offline but other nodes still exist, the Agent will be automatically migrated to another available node. As a result, the registered cluster will become disconnected for a short period of time.
- Scenario 2: If all nodes are taken offline, the Agent cannot be installed. As a result, the registered cluster will become disconnected.
Solution
We recommend that you retain at least one node that runs as expected to ensure the Agent can be installed and thus the cluster can be connected. To resolve the preceding issues, use the following methods:
- Solution 1: For Scenario 1, no additional operations are required. The cluster will become connected after the agent is migrated.
- Solution 2: For Scenario 2, the cluster is disconnected, and nodes cannot be added or published through VKE. Go to the source platform to add or publish nodes. Then, the agent will automatically recover, and the cluster will become connected.
Last updated: 2026.07.23 14:31:46