Skip to content

Commit 6a47979

Browse files
committed
Address comments
1 parent a67d101 commit 6a47979

File tree

3 files changed

+9
-12
lines changed

3 files changed

+9
-12
lines changed

src/current/v25.2/scale-cockroachdb-operator.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -107,12 +107,12 @@ Do not scale down to fewer than 3 nodes. This is considered an anti-pattern on C
107107

108108
## Decommission nodes
109109

110-
When a Kubernetes node is scheduled for removal or maintenance, the {{ site.data.products.cockroachdb-operator }} can be instructed to decommission the node which safely moves data and workloads away before it goes offline.
110+
When a Kubernetes node is scheduled for removal or maintenance, the {{ site.data.products.cockroachdb-operator }} can be instructed to decommission the CockroachDB nodes scheduled on this Kubernetes node. Decommissioning safely moves data and workloads away before the node goes offline.
111111

112112
{{site.data.alerts.callout_info}}
113-
Annotating a CockroachDB node for decommissioning immediately begins the decommission process. The annotation is not a mark for future removal. Once decommissioned, the node is cordoned so no further pods are scheduled on the node.
113+
Once annotated, the Kubernetes node is cordoned so no further pods are scheduled on the node. The annotation is not a mark for future removal, as CockroachDB is decommissioned on the node immediately.
114114

115-
If cluster capacity is limited, replacement pods may remain in the `Pending` state until new nodes are available. This is expected, as the operator prioritizes data safety and full replication over immediate scheduling.
115+
If cluster capacity is limited, replacement pods may remain in the `Pending` state until new nodes are available.
116116
{{site.data.alerts.end}}
117117

118118
The following prerequisites are necessary for the {{ site.data.products.cockroachdb-operator }} to be able to decommission a CockroachDB node:
@@ -126,7 +126,6 @@ The following prerequisites are necessary for the {{ site.data.products.cockroac
126126
args:
127127
- "-enable-k8s-node-controller=true"
128128
~~~
129-
- The role-based access control system must be configured to allow the operator to patch nodes.
130129
- At least one replica of the operator must not be on the target node.
131130
- There must be no under-replicated ranges on the CockroachDB cluster.
132131

src/current/v25.3/scale-cockroachdb-operator.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -107,12 +107,12 @@ Do not scale down to fewer than 3 nodes. This is considered an anti-pattern on C
107107

108108
## Decommission nodes
109109

110-
When a Kubernetes node is scheduled for removal or maintenance, the {{ site.data.products.cockroachdb-operator }} can be instructed to decommission the node which safely moves data and workloads away before it goes offline.
110+
When a Kubernetes node is scheduled for removal or maintenance, the {{ site.data.products.cockroachdb-operator }} can be instructed to decommission the CockroachDB nodes scheduled on this Kubernetes node. Decommissioning safely moves data and workloads away before the node goes offline.
111111

112112
{{site.data.alerts.callout_info}}
113-
Annotating a CockroachDB node for decommissioning immediately begins the decommission process. The annotation is not a mark for future removal. Once decommissioned, the node is cordoned so no further pods are scheduled on the node.
113+
Once annotated, the Kubernetes node is cordoned so no further pods are scheduled on the node. The annotation is not a mark for future removal, as CockroachDB is decommissioned on the node immediately.
114114

115-
If cluster capacity is limited, replacement pods may remain in the `Pending` state until new nodes are available. This is expected, as the operator prioritizes data safety and full replication over immediate scheduling.
115+
If cluster capacity is limited, replacement pods may remain in the `Pending` state until new nodes are available.
116116
{{site.data.alerts.end}}
117117

118118
The following prerequisites are necessary for the {{ site.data.products.cockroachdb-operator }} to be able to decommission a CockroachDB node:
@@ -126,7 +126,6 @@ The following prerequisites are necessary for the {{ site.data.products.cockroac
126126
args:
127127
- "-enable-k8s-node-controller=true"
128128
~~~
129-
- The role-based access control system must be configured to allow the operator to patch nodes.
130129
- At least one replica of the operator must not be on the target node.
131130
- There must be no under-replicated ranges on the CockroachDB cluster.
132131

src/current/v25.4/scale-cockroachdb-operator.md

Lines changed: 3 additions & 4 deletions
Original file line numberDiff line numberDiff line change
@@ -107,12 +107,12 @@ Do not scale down to fewer than 3 nodes. This is considered an anti-pattern on C
107107

108108
## Decommission nodes
109109

110-
When a Kubernetes node is scheduled for removal or maintenance, the {{ site.data.products.cockroachdb-operator }} can be instructed to decommission the node which safely moves data and workloads away before it goes offline.
110+
When a Kubernetes node is scheduled for removal or maintenance, the {{ site.data.products.cockroachdb-operator }} can be instructed to decommission the CockroachDB nodes scheduled on this Kubernetes node. Decommissioning safely moves data and workloads away before the node goes offline.
111111

112112
{{site.data.alerts.callout_info}}
113-
Annotating a CockroachDB node for decommissioning immediately begins the decommission process. The annotation is not a mark for future removal. Once decommissioned, the node is cordoned so no further pods are scheduled on the node.
113+
Once annotated, the Kubernetes node is cordoned so no further pods are scheduled on the node. The annotation is not a mark for future removal, as CockroachDB is decommissioned on the node immediately.
114114

115-
If cluster capacity is limited, replacement pods may remain in the `Pending` state until new nodes are available. This is expected, as the operator prioritizes data safety and full replication over immediate scheduling.
115+
If cluster capacity is limited, replacement pods may remain in the `Pending` state until new nodes are available.
116116
{{site.data.alerts.end}}
117117

118118
The following prerequisites are necessary for the {{ site.data.products.cockroachdb-operator }} to be able to decommission a CockroachDB node:
@@ -126,7 +126,6 @@ The following prerequisites are necessary for the {{ site.data.products.cockroac
126126
args:
127127
- "-enable-k8s-node-controller=true"
128128
~~~
129-
- The role-based access control system must be configured to allow the operator to patch nodes.
130129
- At least one replica of the operator must not be on the target node.
131130
- There must be no under-replicated ranges on the CockroachDB cluster.
132131

0 commit comments

Comments
 (0)