9.2. The OpenStack Cloud Controller Manager (CCM) config map
An OpenStack CCM config map defines how your cluster interacts with your RHOSP cloud. By default, this configuration is stored under the cloud.conf key in the cloud-conf config map in the openshift-cloud-controller-manager namespace.
The cloud-conf config map is generated from the cloud-provider-config config map in the openshift-config namespace.
To change the settings that are described by the cloud-conf config map, modify the cloud-provider-config config map.
As part of this synchronization, the CCM Operator overrides some options. For more information, see "The RHOSP Cloud Controller Manager".
For example:
An example cloud-conf config map
apiVersion: v1
data:
cloud.conf: |
[Global]
secret-name = openstack-credentials
secret-namespace = kube-system
region = regionOne
[LoadBalancer]
use-octavia = True
kind: ConfigMap
metadata:
creationTimestamp: "2022-12-20T17:01:08Z"
name: cloud-conf
namespace: openshift-cloud-controller-manager
resourceVersion: "2519"
uid: cbbeedaf-41ed-41c2-9f37-4885732d3677
- 1
- Set global options by using a
clouds.yamlfile rather than modifying the config map.
The following options are present in the config map. Except when indicated otherwise, they are mandatory for clusters that run on RHOSP.
9.2.1. Load balancer options 링크 복사링크가 클립보드에 복사되었습니다!
CCM supports several load balancer options for deployments that use Octavia.
Neutron-LBaaS support is deprecated.
| Option | Description |
|---|---|
|
|
Whether or not to enable the |
|
|
Optional. The external network used to create floating IP addresses for load balancer virtual IP addresses (VIPs). If there are multiple external networks in the cloud, this option must be set or the user must specify |
|
|
Optional. The external network subnet used to create floating IP addresses for the load balancer VIP. Can be overridden by the service annotation |
|
|
Optional. A name pattern (glob or regular expression if starting with |
|
|
Optional. Tags for the external network subnet used to create floating IP addresses for the load balancer VIP. Can be overridden by the service annotation
If the RHOSP network is configured with sharing disabled, for example, with the |
|
|
The load balancing algorithm used to create the load balancer pool. For the Amphora provider the value can be
For the OVN provider, only the
For the Amphora provider, if using the |
|
|
Optional. Used to specify the provider of the load balancer, for example, |
|
|
Optional. The load balancer API version. Only |
|
| The ID of the Networking service subnet on which load balancer VIPs are created. |
|
|
The ID of the Networking service network on which load balancer VIPs are created. Unnecessary if |
|
|
Whether or not to create a health monitor for the service load balancer. A health monitor is required for services that declare
This option is unsupported if you use RHOSP earlier than version 17 with the |
|
|
The interval in seconds by which probes are sent to members of the load balancer. The default value is |
|
|
The number of successful checks that are required to change the operating status of a load balancer member to |
|
|
The time in seconds that a monitor waits to connect to the back end before it times out. The default value is |
|
|
Whether or not to create an internal load balancer without floating IP addresses. The default value is |
|
| This is a config section that comprises a set of options:
The behavior of these options is the same as that of the identically named options in the load balancer section of the CCM config file.
You can set the |
|
|
The maximum number of services that can share a load balancer. The default value is |