Skip to content

Commit

Permalink
Add a section in the doc about nodeSelector
Browse files Browse the repository at this point in the history
  • Loading branch information
gthiemonge committed Dec 5, 2024
1 parent 1a6e1b7 commit 74de699
Showing 1 changed file with 21 additions and 0 deletions.
21 changes: 21 additions & 0 deletions MANAGEMENT_NETWORK.md
Original file line number Diff line number Diff line change
Expand Up @@ -316,3 +316,24 @@ The `fixed_ips`, `device_id` and `device_owner` are all of interest:
* `fixed_ips` will match the IP for the `interfaces_info` of the `octavia-link-router`
* `device_id` will match the ID for the `octavia-link-router`
* `device_owner` indicates that OpenStack is using the port as a router interface

## Running the Octavia Amphora Controller Pods on specific Nodes

By default, the Amphora Controller pods are deployed on all the nodes of a
cluster. In case of a cluster with a high number of nodes, it's not needed,
it's preferable to use only 3 nodes.
An admin can limit the number of instances of these services by using
a `nodeSelector`. They add a label on specific nodes to indicate that they will
host the Octavia services.

For instance, set a label on master-2:

```shell
$ oc patch nodes master-2 --type merge --patch '{"metadata":{"labels":{"openstack.org/octavia-controller":""}}}'
```

Make the Octavia services run only on these nodes:

```shell
$ oc patch -n openstack openstackcontrolplane controlplane --type merge --patch '{"spec":{"octavia":{"template":{"nodeSelector":{"openstack.org/octavia-controller":""}}}}}'
```

0 comments on commit 74de699

Please sign in to comment.