mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-26 13:08:11 +00:00
Remove version-latest dir
Originally added due to some unexpected versioning behavior that's no longer reproducible Apply suggestions from code review Co-authored-by: Marty Hernandez Avedon <martyavedon@gmail.com>
This commit is contained in:
co-authored by
Marty Hernandez Avedon
parent
e60feac44c
commit
5c083c320a
+1
-1
@@ -108,7 +108,7 @@ This section covers three methods to reconfigure Rancher agents to trust the pri
|
||||
|
||||
#### Why is this step required?
|
||||
|
||||
When Rancher is configured with a certificate signed by a private CA, the CA certificate chain is downloaded into Rancher agent containers. Agents compare the checksum of the downloaded certificate against the `CATTLE_CA_CHECKSUM` environment variable. This means that, when the private CA certificate is changed on Rancher server side, the environvment variable `CATTLE_CA_CHECKSUM` must be updated accordingly.
|
||||
When Rancher is configured with a certificate signed by a private CA, the CA certificate chain is downloaded into Rancher agent containers. Agents compare the checksum of the downloaded certificate against the `CATTLE_CA_CHECKSUM` environment variable. This means that, when the private CA certificate is changed on Rancher server side, the environment variable `CATTLE_CA_CHECKSUM` must be updated accordingly.
|
||||
|
||||
#### Which method should I choose?
|
||||
|
||||
|
||||
+1
-1
@@ -85,7 +85,7 @@ Private GKE clusters are supported. Note: This advanced setup can require more s
|
||||
For details on configuring GKE clusters in Rancher, see [this page.](../../../../pages-for-subheaders/gke-cluster-configuration.md)
|
||||
## Updating Kubernetes Version
|
||||
|
||||
The Kubernetes version of a cluster can be upgraded to any version available in the region or zone fo the GKE cluster. Upgrading the master Kubernetes version does not automatically upgrade worker nodes. Nodes can be upgraded independently.
|
||||
The Kubernetes version of a cluster can be upgraded to any version available in the region or zone for the GKE cluster. Upgrading the master Kubernetes version does not automatically upgrade worker nodes. Nodes can be upgraded independently.
|
||||
|
||||
:::note
|
||||
|
||||
|
||||
-2
@@ -13,10 +13,8 @@ For Kubernetes v1.21 and up, the NGINX Ingress controller no longer runs in host
|
||||
|
||||
Because of this change to the controller, the default RKE1 behavior no longer sets `hostNetwork` to `true`. However, you must set `hostNetwork` to `true` for TCP- and UDP-based Services to work. To do so, [edit](../../../../reference-guides/cluster-configuration/rancher-server-configuration/rke1-cluster-configuration.md#editing-clusters-with-yaml) the cluster's YAML and follow the steps in the [official RKE1 doccumention](https://rke.docs.rancher.com/config-options/add-ons/ingress-controllers#configuring-network-options).
|
||||
|
||||
|
||||
:::
|
||||
|
||||
|
||||
- [Specify a hostname to use](#specify-a-hostname-to-use)
|
||||
- [Certificates](#certificates)
|
||||
- [Labels and Annotations](#labels-and-annotations)
|
||||
|
||||
-2
@@ -52,8 +52,6 @@ If you have a cluster with DRS enabled, setting up [VM-VM Affinity Rules](https:
|
||||
|
||||
## Creating a vSphere Cluster
|
||||
|
||||
The a vSphere cluster is created in Rancher depends on the Rancher version.
|
||||
|
||||
1. [Create your cloud credentials](#1-create-your-cloud-credentials)
|
||||
2. [Create a node template with your cloud credentials](#2-create-a-node-template-with-your-cloud-credentials)
|
||||
3. [Create a cluster with node pools using the node template](#3-create-a-cluster-with-node-pools-using-the-node-template)
|
||||
|
||||
Reference in New Issue
Block a user