Continental Innovates with Rancher and Kubernetes
After you provision a Kubernetes cluster using Rancher, you can still edit options and settings for the cluster.
For information on editing cluster membership, go to this page.
The options and settings available for an existing cluster change based on the method that you used to provision it. For example, only clusters provisioned by RKE have Cluster Options available for editing.
The following table summarizes the options and settings available for each cluster type:
* Cluster configuration options can’t be edited for imported clusters, except for K3s clusters.
To edit your cluster, open the Global view, make sure the Clusters tab is selected, and then select ⋮ > Edit for the cluster that you want to edit.
In clusters launched by RKE, you can edit any of the remaining options that follow.
Note that these options are not available for imported clusters or hosted Kubernetes clusters.
Instead of using the Rancher UI to choose Kubernetes options for the cluster, advanced users can create an RKE config file. Using a config file allows you to set any of the options available in an RKE installation, except for system_images configuration, by specifying them in YAML.
For an example of RKE config file syntax, see the RKE documentation.
For the complete reference of configurable options for RKE Kubernetes clusters in YAML, see the RKE documentation.
In Rancher v2.0.0-v2.2.x, the config file is identical to the cluster config file for the Rancher Kubernetes Engine, which is the tool Rancher uses to provision clusters. In Rancher v2.3.0, the RKE information is still included in the config file, but it is separated from other options, so that the RKE cluster config options are nested under the rancher_kubernetes_engine_config directive. For more information, see the cluster configuration reference.
rancher_kubernetes_engine_config
Note: In Rancher v2.0.5 and v2.0.6, the names of services in the Config File (YAML) should contain underscores only: kube_api and kube_controller.
kube_api
kube_controller
Clusters that were created before Kubernetes 1.16 will have an ingress-nginx updateStrategy of OnDelete. Clusters that were created with Kubernetes 1.16 or newer will have RollingUpdate.
ingress-nginx
updateStrategy
OnDelete
RollingUpdate
If the updateStrategy of ingress-nginx is OnDelete, you will need to delete these pods to get the correct version for your deployment.