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
Optionally, a custom certificate may be sourced via `os-certAuthorityPath` (path to a PEM file inside the plugin container). By default, the usual TLS verification is performed. To override this behavior and accept insecure certificates, set `os-TLSInsecure` to `true` (defaults to `false`).
82
82
83
+
For a client TLS authentication use both `os-clientCertPath` and `os-clientKeyPath` (paths to TLS keypair PEM files inside the plugin container).
84
+
83
85
### Topology-aware dynamic provisioning
84
86
85
87
Topology-aware dynamic provisioning makes it possible to reliably provision and use shares that are _not_ equally accessible from all compute nodes due to storage topology constraints.
Copy file name to clipboardExpand all lines: docs/using-openstack-cloud-controller-manager.md
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -94,6 +94,10 @@ The options in `Global` section are used for openstack-cloud-controller-manager
94
94
Required. Keystone service URL, e.g. http://128.110.154.166/identity
95
95
* `ca-file`
96
96
Optional. CA certificate bundle file for communication with Keystone service, this is required when using the https protocol in the Keystone service URL.
97
+
* `cert-file`
98
+
Optional. Client certificate path used for the client TLS authentication.
99
+
* `key-file`
100
+
Optional. Client private key path used for the client TLS authentication.
97
101
* `username`
98
102
Keystone user name. If you are using [Keystone application credential](https://docs.openstack.org/keystone/latest/user/application_credentials.html), this option is not required.
0 commit comments