Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions modules/cluster-cloud-controller-config-osp.adoc
Original file line number Diff line number Diff line change
Expand Up @@ -154,15 +154,15 @@ For the Amphora provider, if using the `LEAST_CONNECTIONS` or `SOURCE_IP` method
| Optional. The load balancer API version. Only `"v2"` is supported.

| `subnet-id`
| The ID of the Networking service subnet on which load balancer VIPs are created.
| The ID of the Networking service subnet on which load balancer VIPs are created. For dual stack deployments, leave this option unset. The OpenStack cloud provider automatically selects which subnet to use for a load balancer.

// This ID is also used to create pool members if `member-subnet-id` is not set.

// | `member-subnet-id`
// | ID of the Neutron network on which to create the members of the load balancer. The load balancer gets another network port on this subnet. Defaults to `subnet-id` if not set.

| `network-id`
| The ID of the Networking service network on which load balancer VIPs are created. Unnecessary if `subnet-id` is set.
| The ID of the Networking service network on which load balancer VIPs are created. Unnecessary if `subnet-id` is set. If this property is not set, the network is automatically selected based on the network that cluster nodes use.

// | `manage-security-groups`
// | If the Neutron security groups should be managed separately. Default: false
Expand Down Expand Up @@ -321,4 +321,4 @@ CCM searches for the file in the following places:

| `cloud`
| The named cloud in the `clouds.yaml` file that you want to use. It is used if the `use-clouds` option is set to `true`.
|===
|===