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
+7-5Lines changed: 7 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -207,11 +207,13 @@ Request Body:
207
207
Reference to a tls container. This option works with Octavia, when this option is set then the cloud provider will create an Octavia Listener of type `TERMINATED_HTTPS` for a TLS Terminated loadbalancer.
208
208
Format for tls container ref: `https://{keymanager_host}/v1/containers/{uuid}`
209
209
210
+
When `container-store` parameter is set to `external` format for `default-tls-container-ref` could be any string.
211
+
210
212
Not supported when `lb-provider=ovn` is configured in openstack-cloud-controller-manager.
211
213
212
214
-`loadbalancer.openstack.org/load-balancer-id`
213
215
214
-
This annotation is automatically added to the Service if it's not specified when creating. After the Service is created successfully it shouldn't be changed, otherwise the Service won't behave as expected.
216
+
This annotation is automatically added to the Service if it's not specified when creating. After the Service is created successfully it shouldn't be changed, otherwise the Service won't behave as expected.
215
217
216
218
If this annotation is specified with a valid cloud load balancer ID when creating Service, the Service is reusing this load balancer rather than creating another one. Again, it shouldn't be changed after the Service is created.
217
219
@@ -413,9 +415,9 @@ To enable PROXY protocol support, the openstack-cloud-controller-manager config
Copy file name to clipboardExpand all lines: docs/openstack-cloud-controller-manager/using-openstack-cloud-controller-manager.md
+12-5Lines changed: 12 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -177,18 +177,18 @@ Although the openstack-cloud-controller-manager was initially implemented with N
177
177
178
178
* `use-octavia`
179
179
Whether or not to use Octavia for LoadBalancer type of Service implementation instead of using Neutron-LBaaS. Default: true
180
-
180
+
181
181
* `floating-network-id`
182
182
Optional. The external network used to create floating IP for the load balancer VIP. If there are multiple external networks in the cloud, either this option must be set or user must specify `loadbalancer.openstack.org/floating-network-id` in the Service annotation.
183
183
184
184
* `floating-subnet-id`
185
185
Optional. The external network subnet used to create floating IP for the load balancer VIP. Can be overridden by the Service annotation `loadbalancer.openstack.org/floating-subnet-id`.
186
186
187
187
* `floating-subnet`
188
-
Optional. A name pattern (glob or regexp if starting with `~`) for the external network subnet used to create floating IP for the load balancer VIP. Can be overridden by the Service annotation `loadbalancer.openstack.org/floating-subnet`. If multiple subnets match the first one with still available IPs is used.
188
+
Optional. A name pattern (glob or regexp if starting with `~`) for the external network subnet used to create floating IP for the load balancer VIP. Can be overridden by the Service annotation `loadbalancer.openstack.org/floating-subnet`. If multiple subnets match the first one with still available IPs is used.
189
189
190
190
* `floating-subnet-tags`
191
-
Optional. Tags for the external network subnet used to create floating IP for the load balancer VIP. Can be overridden by the Service annotation `loadbalancer.openstack.org/floating-subnet-tags`. If multiple subnets match the first one with still available IPs is used.
191
+
Optional. Tags for the external network subnet used to create floating IP for the load balancer VIP. Can be overridden by the Service annotation `loadbalancer.openstack.org/floating-subnet-tags`. If multiple subnets match the first one with still available IPs is used.
192
192
193
193
* `lb-method`
194
194
The load balancing algorithm used to create the load balancer pool. The value can be `ROUND_ROBIN`, `LEAST_CONNECTIONS`, or `SOURCE_IP`. Default: `ROUND_ROBIN`
@@ -227,7 +227,7 @@ Although the openstack-cloud-controller-manager was initially implemented with N
227
227
228
228
* `cascade-delete`
229
229
Determines whether or not to perform cascade deletion of load balancers. Default: true.
230
-
230
+
231
231
* `flavor-id`
232
232
The id of the loadbalancer flavor to use. Uses octavia default if not set.
233
233
@@ -243,7 +243,7 @@ Although the openstack-cloud-controller-manager was initially implemented with N
243
243
* floating-subnet-tags. The same with `floating-subnet-tags` option above.
244
244
* network-id. The same with `network-id` option above.
245
245
* subnet-id. The same with `subnet-id` option above.
246
-
246
+
247
247
* `enable-ingress-hostname`
248
248
249
249
Used with proxy protocol (set by annotation `loadbalancer.openstack.org/proxy-protocol: "true"`) by adding a dns suffix (nip.io) to the load balancer IP address. Default false.
@@ -260,6 +260,13 @@ Although the openstack-cloud-controller-manager was initially implemented with N
260
260
Reference to a tls container. This option works with Octavia, when this option is set then the cloud provider will create an Octavia Listener of type TERMINATED_HTTPS for a TLS Terminated loadbalancer.
261
261
262
262
Format for tls container ref: `https://{keymanager_host}/v1/containers/{uuid}`
263
+
Check `container-store` parameter if you want to disable validation.
264
+
265
+
* `container-store`
266
+
Optional. Used to specify the store of the tls-container-ref, e.g. "barbican" or "external" - other store will cause a warning log.
267
+
Default value - `barbican` - existence of tls container ref would always be performed.
268
+
269
+
If set to `external` format for tls container ref will not be validated.
263
270
264
271
* `max-shared-lb`
265
272
The maximum number of Services that share a load balancer. Default: 2
// AddExtraFlags is called by the main package to add component specific command line flags
60
63
funcAddExtraFlags(fs*pflag.FlagSet) {
61
64
fs.StringArrayVar(&userAgentData, "user-agent", nil, "Extra data to add to gophercloud user-agent. Use multiple times to add more than one component.")
@@ -98,6 +101,7 @@ type LoadBalancerOpts struct {
98
101
EnableIngressHostnamebool`gcfg:"enable-ingress-hostname"`// Used with proxy protocol by adding a dns suffix to the load balancer IP address. Default false.
99
102
IngressHostnameSuffixstring`gcfg:"ingress-hostname-suffix"`// Used with proxy protocol by adding a dns suffix to the load balancer IP address. Default nip.io.
100
103
MaxSharedLBint`gcfg:"max-shared-lb"`// Number of Services in maximum can share a single load balancer. Default 2
104
+
ContainerStorestring`gcfg:"container-store"`// Used to specify the store of the tls-container-ref
101
105
// revive:disable:var-naming
102
106
TlsContainerRefstring`gcfg:"default-tls-container-ref"`// reference to a tls container
0 commit comments