Continental Innovates with Rancher and Kubernetes
To enable the Openstack cloud provider, besides setting the name as openstack, there are specific configuration options that must be set. The Openstack configuration options are grouped into different sections.
openstack
cloud_provider: name: openstack openstackCloudProvider: global: username: xxxxxxxxxxxxxx password: xxxxxxxxxxxxxx auth-url: https://1.2.3.4/identity/v3 tenant-id: xxxxxxxxxxxxxx domain-id: xxxxxxxxxxxxxx load_balancer: subnet-id: xxxxxxxxxxxxxx block_storage: ignore-volume-az: true route: router-id: xxxxxxxxxxxxxx metadata: search-order: xxxxxxxxxxxxxx
The OpenStack cloud provider uses the instance name (as determined from OpenStack metadata) as the name of the Kubernetes Node object, you must override the Kubernetes name on the node by setting the hostname_override for each node. If you do not set the hostname_override, the Kubernetes node name will be set as the address, which will cause the Openstack cloud provider to fail.
hostname_override
address
The Openstack configuration options are divided into 5 groups.
These are the options that are available under the global directive.
global
These are the options that are available under the load_balancer directive.
load_balancer
create-monitor
These are the options that are available under the block_storage directive.
block_storage
This is the option that is available under the route directive.
route
These are the options that are available under the metadata directive.
metadata
For more information of Openstack configurations options please refer to the official Kubernetes documentation.