You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/openstack-cloud-controller-manager/expose-applications-using-loadbalancer-type-service.md
+6Lines changed: 6 additions & 0 deletions
Original file line number
Diff line number
Diff line change
@@ -236,6 +236,12 @@ Request Body:
236
236
This annotation is automatically added and it contains the floating ip address of the load balancer service.
237
237
When using `loadbalancer.openstack.org/hostname` annotation it is the only place to see the real address of the load balancer.
238
238
239
+
-`loadbalancer.openstack.org/node-selector`
240
+
241
+
A set of key=value annotations used to filter nodes for targeting by the load balancer. When defined, only nodes that match all the specified key=value annotations will be targeted. If an annotation includes only a key without a value, the filter will check only for the existence of the key on the node. If the value is not set, the `node-selector` value defined in the OCCM configuration is applied.
242
+
243
+
Example: To filter nodes with the labels `env=production` and `region=default`, set the `loadbalancer.openstack.org/node-selector` annotation to `env=production, region=default`
244
+
239
245
### Switching between Floating Subnets by using preconfigured Classes
240
246
241
247
If you have multiple `FloatingIPPools` and/or `FloatingIPSubnets` it might be desirable to offer the user logical meanings for `LoadBalancers` like `internetFacing` or `DMZ` instead of requiring the user to select a dedicated network or subnet ID at the service object level as an annotation.
Copy file name to clipboardExpand all lines: docs/openstack-cloud-controller-manager/using-openstack-cloud-controller-manager.md
+18-1Lines changed: 18 additions & 1 deletion
Original file line number
Diff line number
Diff line change
@@ -207,7 +207,7 @@ Although the openstack-cloud-controller-manager was initially implemented with N
207
207
* `ROUND_ROBIN` (default)
208
208
* `LEAST_CONNECTIONS`
209
209
* `SOURCE_IP`
210
-
210
+
211
211
If `lb-provider` is set to "ovn" the value must be set to `SOURCE_IP_PORT`.
212
212
213
213
* `lb-provider`
@@ -248,6 +248,23 @@ Although the openstack-cloud-controller-manager was initially implemented with N
248
248
* `internal-lb`
249
249
Determines whether or not to create an internal load balancer (no floating IP) by default. Default: false.
250
250
251
+
* `node-selector`
252
+
A comma separated list of key=value annotations used to filter nodes for targeting by the load balancer. When defined, only nodes that match all the specified key=value annotations will be targeted. If an annotation includes only a key without a value, the filter will check only for the existence of the key on the node. When node-selector is not set (default value), all nodes will be added as members to a load balancer pool.
253
+
254
+
Note: This configuration option can be overridden with the `loadbalancer.openstack.org/node-selector` service annotation. Refer to [Exposing applications using services of LoadBalancer type](./expose-applications-using-loadbalancer-type-service.md)
255
+
256
+
Example: To filter nodes with the labels `env=production` and `region=default`, set the `node-selector` as follows:
257
+
258
+
```
259
+
node-selector="env=production, region=default"
260
+
```
261
+
262
+
Example: To filter nodes that have the key `env` with any value and the key `region` specifically set to `default`, set the `node-selector` as follows:
263
+
264
+
```
265
+
node-selector="env, region=default"
266
+
```
267
+
251
268
* `cascade-delete`
252
269
Determines whether or not to perform cascade deletion of load balancers. Default: true.
// getStringFromServiceAnnotation searches a given v1.Service for a specific annotationKey and either returns the annotation's value or a specified defaultSetting
NodeSelectorstring`gcfg:"node-selector"`// If specified, the loadbalancer members will be assined only from nodes list filtered by node-selector labels
0 commit comments