mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-24 20:18:18 +00:00
Update OpenStack typo.
This commit is contained in:
@@ -5,6 +5,6 @@ aliases:
|
||||
- /os/v1.x/en/installation/running-rancheros/cloud/openstack
|
||||
---
|
||||
|
||||
As of v0.5.0, RancherOS releases include an Openstack image that can be found on our [releases page](https://github.com/rancher/os/releases). The image format is [QCOW3](https://wiki.qemu.org/Features/Qcow3#Fully_QCOW2_backwards-compatible_feature_set) that is backward compatible with QCOW2.
|
||||
As of v0.5.0, RancherOS releases include an OpenStack image that can be found on our [releases page](https://github.com/rancher/os/releases). The image format is [QCOW3](https://wiki.qemu.org/Features/Qcow3#Fully_QCOW2_backwards-compatible_feature_set) that is backward compatible with QCOW2.
|
||||
|
||||
When launching an instance using the image, you must enable **Advanced Options** -> **Configuration Drive** and in order to use a [cloud-config]({{< baseurl >}}/os/v1.x/en/configuration/#cloud-config) file.
|
||||
|
||||
+1
-1
@@ -43,4 +43,4 @@ The `Custom` cloud provider is available if you want to configure any [Kubernete
|
||||
For the custom cloud provider option, you can refer to the [RKE docs]({{<baseurl>}}/rke/latest/en/config-options/cloud-providers/) on how to edit the yaml file for your specific cloud provider. There are specific cloud providers that have more detailed configuration :
|
||||
|
||||
* [vSphere]({{<baseurl>}}/rke/latest/en/config-options/cloud-providers/vsphere/)
|
||||
* [Openstack]({{<baseurl>}}/rke/latest/en/config-options/cloud-providers/openstack/)
|
||||
* [OpenStack]({{<baseurl>}}/rke/latest/en/config-options/cloud-providers/openstack/)
|
||||
|
||||
@@ -43,4 +43,4 @@ The `Custom` cloud provider is available if you want to configure any [Kubernete
|
||||
For the custom cloud provider option, you can refer to the [RKE docs]({{<baseurl>}}/rke/latest/en/config-options/cloud-providers/) on how to edit the yaml file for your specific cloud provider. There are specific cloud providers that have more detailed configuration :
|
||||
|
||||
* [vSphere]({{<baseurl>}}/rke/latest/en/config-options/cloud-providers/vsphere/)
|
||||
* [Openstack]({{<baseurl>}}/rke/latest/en/config-options/cloud-providers/openstack/)
|
||||
* [OpenStack]({{<baseurl>}}/rke/latest/en/config-options/cloud-providers/openstack/)
|
||||
|
||||
@@ -43,4 +43,4 @@ The `Custom` cloud provider is available if you want to configure any [Kubernete
|
||||
For the custom cloud provider option, you can refer to the [RKE docs]({{<baseurl>}}/rke/latest/en/config-options/cloud-providers/) on how to edit the yaml file for your specific cloud provider. There are specific cloud providers that have more detailed configuration :
|
||||
|
||||
* [vSphere]({{<baseurl>}}/rke/latest/en/config-options/cloud-providers/vsphere/)
|
||||
* [Openstack]({{<baseurl>}}/rke/latest/en/config-options/cloud-providers/openstack/)
|
||||
* [OpenStack]({{<baseurl>}}/rke/latest/en/config-options/cloud-providers/openstack/)
|
||||
|
||||
@@ -1,9 +1,9 @@
|
||||
---
|
||||
title: Openstack Cloud Provider
|
||||
title: OpenStack Cloud Provider
|
||||
weight: 253
|
||||
---
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
```yaml
|
||||
cloud_provider:
|
||||
@@ -27,11 +27,11 @@ cloud_provider:
|
||||
|
||||
## Overriding the hostname
|
||||
|
||||
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.
|
||||
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.
|
||||
|
||||
## Openstack Configuration Options
|
||||
## OpenStack Configuration Options
|
||||
|
||||
The Openstack configuration options are divided into 5 groups.
|
||||
The OpenStack configuration options are divided into 5 groups.
|
||||
|
||||
* Global
|
||||
* Load Balancer
|
||||
@@ -103,4 +103,4 @@ These are the options that are available under the `metadata` directive.
|
||||
| search-order | string | |
|
||||
| request-timeout | int | |
|
||||
|
||||
For more information of Openstack configurations options please refer to the official Kubernetes [documentation](https://kubernetes.io/docs/concepts/cluster-administration/cloud-providers/#openstack).
|
||||
For more information of OpenStack configurations options please refer to the official Kubernetes [documentation](https://kubernetes.io/docs/concepts/cluster-administration/cloud-providers/#openstack).
|
||||
|
||||
Reference in New Issue
Block a user