Skip to content

Commit

Permalink
remove original version of pending paragraph
Browse files Browse the repository at this point in the history
  • Loading branch information
vincentportella committed Aug 26, 2024
1 parent 22a1ec5 commit 2971e21
Showing 1 changed file with 0 additions and 2 deletions.
2 changes: 0 additions & 2 deletions docs/cycling/README.md
Original file line number Diff line number Diff line change
Expand Up @@ -28,8 +28,6 @@ The CycleNodeRequest CRD handles a request to cycle nodes belonging to a specifi

2. Validate the CycleNodeRequest object's parameters, and if valid, transition the object to **Pending**.

3. In the **Pending** phase, store the nodes that will need to be cycled so we can keep track of them. Describe the node group in the cloud provider and check it to ensure it matches the nodes in Kubernetes. It will wait for a brief period for the nodes to match, in case the cluster has just scaled up or down. Transition the object to **Initialised**.

3. In the **Pending** phase, store the nodes that will need to be cycled so we can keep track of them. Describe the node group in the cloud provider and check it to ensure it matches the nodes in Kubernetes. It will wait for a brief period and proactively clean up any orphaned node objects, re-attach any instances that have been detached from the cloud provider node group, and then wait for the nodes to match in case the cluster has just scaled up or down. Transition the object to **Initialised**.

4. In the **Initialised** phase, detach a number of nodes (governed by the concurrency of the CycleNodeRequest) from the node group. This will trigger the cloud provider to add replacement nodes for each. Transition the object to **ScalingUp**. If there are no more nodes to cycle then transition to **Successful**.
Expand Down

0 comments on commit 2971e21

Please sign in to comment.