mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-09-25 20:48:11 +00:00
Update _index.md
This commit is contained in:
@@ -111,7 +111,10 @@ The last line should read `Finished building Kubernetes cluster successfully` to
|
||||
|
||||
### Kubernetes Cluster State
|
||||
|
||||
Prior to rke v0.2.0, RKE saves the cluster state which consists of the cluster configuration file `cluster.yml` and components certificates in kubernetes cluster as secrets, in v0.2.0 RKE creates a `.rkestate` file in the same directory that has the cluster configuration file, this file contains the current state of the cluster including the RKE config and the certificates, it is essential to keep this file to be able to update the cluster or perform any operation on it.
|
||||
The Kubernetes cluster state, which consists of the cluster configuration file `cluster.yml` and components certificates in Kubernetes cluster, is saved by RKE, but depending on your RKE version, the cluster state is saved differently.
|
||||
|
||||
As of v0.2.0, RKE creates a `.rkestate` file in the same directory that has the cluster configuration file `cluster.yml`. The `.rkestate` file contains the current state of the cluster including the RKE configuration and the certificates. It is required to keep this file in order to update the cluster or perform any operation on it through RKE.
|
||||
|
||||
```
|
||||
$ tree -L 1
|
||||
.
|
||||
@@ -119,6 +122,9 @@ $ tree -L 1
|
||||
├── cluster.yml
|
||||
├── kube_config_cluster.yml
|
||||
```
|
||||
|
||||
Prior to v0.2.0, RKE saved the Kubernetes cluster state as a secret. When updating the state, RKE pulls the secret, updates/changes the state and saves a new secret.
|
||||
|
||||
### Interacting with your Kubernetes cluster
|
||||
|
||||
In order to start interacting with your Kubernetes cluster, you will use a different binary called `kubectl`. You will need to [install kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/) on your local machine. You can connect to the RKE created cluster by using the `kube_config_cluster.yml` that was generated when you deployed Kubernetes.
|
||||
|
||||
Reference in New Issue
Block a user