Skip to content

Commit 6c04be3

Browse files
committed
[docs] add more uses cases to node-selector service annotation
1 parent 53a4505 commit 6c04be3

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

docs/openstack-cloud-controller-manager/using-openstack-cloud-controller-manager.md

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -155,7 +155,7 @@ The options in `Global` section are used for openstack-cloud-controller-manager
155155
* `application-credential-secret`
156156
The secret of an application credential to authenticate with.
157157
* `tls-insecure`
158-
If set to `true`, then the servers certificate will not be verified. Default is `false`.
158+
If set to `true`, then the server's certificate will not be verified. Default is `false`.
159159
160160
### Networking
161161
@@ -265,6 +265,12 @@ Although the openstack-cloud-controller-manager was initially implemented with N
265265
node-selector="env, region=default"
266266
```
267267
268+
See also the Kubernetes annotation [`node.kubernetes.io/exclude-from-external-load-balancers`](https://kubernetes.io/docs/reference/labels-annotations-taints/#node-kubernetes-io-exclude-from-external-load-balancers). When this annotation is set to `true`, the node is excluded from the load balancer pool.
269+
270+
This annotation also triggers the Cloud Controller Manager to execute the `EnsureLoadBalancer` method to reconcile the LoadBalancer. If a node was already part of the cluster and its label was later modified after the service's `node-selector` annotation was changed, you can explicitly assign `node.kubernetes.io/exclude-from-external-load-balancers: "false"` to a node to force the Cloud Controller Manager to reconcile the LoadBalancer pool.
271+
272+
For example, if a service has `node-selector="env=production"` and a node is labeled `env=development`, updating the node's label to `env=production` will not automatically add it to the LoadBalancer pool. In such cases, setting `node.kubernetes.io/exclude-from-external-load-balancers: "false"` to the node ensures that the Cloud Controller Manager re-evaluates the node's eligibility and updates the LoadBalancer configuration accordingly.
273+
268274
* `cascade-delete`
269275
Determines whether or not to perform cascade deletion of load balancers. Default: true.
270276

0 commit comments

Comments
 (0)