Skip to content

Commit 74de699

Browse files
committed
Add a section in the doc about nodeSelector
1 parent 1a6e1b7 commit 74de699

File tree

1 file changed

+21
-0
lines changed

1 file changed

+21
-0
lines changed

MANAGEMENT_NETWORK.md

Lines changed: 21 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -316,3 +316,24 @@ The `fixed_ips`, `device_id` and `device_owner` are all of interest:
316316
* `fixed_ips` will match the IP for the `interfaces_info` of the `octavia-link-router`
317317
* `device_id` will match the ID for the `octavia-link-router`
318318
* `device_owner` indicates that OpenStack is using the port as a router interface
319+
320+
## Running the Octavia Amphora Controller Pods on specific Nodes
321+
322+
By default, the Amphora Controller pods are deployed on all the nodes of a
323+
cluster. In case of a cluster with a high number of nodes, it's not needed,
324+
it's preferable to use only 3 nodes.
325+
An admin can limit the number of instances of these services by using
326+
a `nodeSelector`. They add a label on specific nodes to indicate that they will
327+
host the Octavia services.
328+
329+
For instance, set a label on master-2:
330+
331+
```shell
332+
$ oc patch nodes master-2 --type merge --patch '{"metadata":{"labels":{"openstack.org/octavia-controller":""}}}'
333+
```
334+
335+
Make the Octavia services run only on these nodes:
336+
337+
```shell
338+
$ oc patch -n openstack openstackcontrolplane controlplane --type merge --patch '{"spec":{"octavia":{"template":{"nodeSelector":{"openstack.org/octavia-controller":""}}}}}'
339+
```

0 commit comments

Comments
 (0)