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/cinder-csi-plugin/using-cinder-csi-plugin.md
+2Lines changed: 2 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -116,6 +116,8 @@ These configuration options pertain to block storage and should appear in the `[
116
116
Optional. Set to `true`, to rescan block device and verify its size before expanding the filesystem. Not all hypervizors have a /sys/class/block/XXX/device/rescan location, therefore if you enable this option and your hypervizor doesn't support this, you'll get a warning log on resize event. It is recommended to disable this option in this case. Defaults to `false`
117
117
*`ignore-volume-az`
118
118
Optional. When `Topology` feature enabled, by default, PV volume node affinity is populated with volume accessible topology, which is volume AZ. But, some of the openstack users do not have compute zones named exactly the same as volume zones. This might cause pods to go in pending state as no nodes available in volume AZ. Enabling `ignore-volume-az=true`, ignores volumeAZ and schedules on any of the available node AZ. Default `false`. Check `cross_az_attach` in [nova configuration](https://docs.openstack.org/nova/latest/configuration/config.html) for further information.
119
+
*`ignore-volume-microversion`
120
+
Optional. Set to `true` only when your cinder microversion is older than 3.34. This might cause some features to not work as expected, but aims to allow basic operations like creating a volume.
119
121
120
122
### Metadata
121
123
These configuration options pertain to metadata and should appear in the `[Metadata]` section of the `$CLOUD_CONFIG` file.
Copy file name to clipboardExpand all lines: docs/openstack-cloud-controller-manager/expose-applications-using-loadbalancer-type-service.md
+6-2Lines changed: 6 additions & 2 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -108,7 +108,7 @@ Request Body:
108
108
109
109
-`loadbalancer.openstack.org/class`
110
110
111
-
The name of a preconfigured class in the config file. If provided, this config options included in the class section take precedence over the annotations of floating-subnet-id and floating-network-id. See the section below for how it works.
111
+
The name of a preconfigured class in the config file. If provided, this config options included in the class section take precedence over the annotations of floating-subnet-id, floating-network-id, network-id, subnet-id and member-subnet-id . See the section below for how it works.
112
112
113
113
-`loadbalancer.openstack.org/subnet-id`
114
114
@@ -223,6 +223,10 @@ Request Body:
223
223
224
224
If this annotation is specified, the other annotations which define the load balancer features will be ignored.
225
225
226
+
-`loadbalancer.openstack.org/hostname`
227
+
228
+
This annotations explicitly sets a hostname in the status of the load balancer service.
229
+
226
230
### Switching between Floating Subnets by using preconfigured Classes
227
231
228
232
If you have multiple `FloatingIPPools` and/or `FloatingIPSubnets` it might be desirable to offer the user logical meanings for `LoadBalancers` like `internetFacing` or `DMZ` instead of requiring the user to select a dedicated network or subnet ID at the service object level as an annotation.
@@ -343,7 +347,7 @@ This requires that not only the proxy server(e.g. NGINX) should support PROXY pr
343
347
344
348
This guide uses nginx-ingress-controller as an example.
345
349
346
-
To enable PROXY protocol support, the openstack-cloud-controller-manager config option [enable-ingress-hostname](./using-openstack-cloud-controller-manager.md#load-balancer) should set to `true`.
350
+
To enable PROXY protocol support, the either the openstack-cloud-controller-manager config option [enable-ingress-hostname](./using-openstack-cloud-controller-manager.md#load-balancer) should set to `true` or an explicit hostname should be set on the load balancer service via [annotation](./expose-applications-using-loadbalancer-type-service.md#service-annotations) `loadbalancer.openstack.org/hostname`.
0 commit comments