From 9a04d57094da30c4b7d98eb84834f976f96caf83 Mon Sep 17 00:00:00 2001 From: Mark Bishop Date: Fri, 18 May 2018 15:49:53 -0700 Subject: [PATCH] made changes requested by Will and removed draft flags --- .../v2.x/en/installation/after-installation/_index.md | 1 - .../etcd-backup-and-restoration/_index.md | 7 +++---- content/rancher/v2.x/en/upgrades/_index.md | 1 - .../rancher/v2.x/en/upgrades/ha-server-upgrade/_index.md | 5 ++--- .../rancher/v2.x/en/upgrades/single-node-upgrade/_index.md | 7 ++----- 5 files changed, 7 insertions(+), 14 deletions(-) diff --git a/content/rancher/v2.x/en/installation/after-installation/_index.md b/content/rancher/v2.x/en/installation/after-installation/_index.md index 051b394bcf8..f9935d7a4f5 100644 --- a/content/rancher/v2.x/en/installation/after-installation/_index.md +++ b/content/rancher/v2.x/en/installation/after-installation/_index.md @@ -1,6 +1,5 @@ --- title: After Installation weight: 360 -draft: true --- This section contains information about how to perform system maintenance on your Rancher install. diff --git a/content/rancher/v2.x/en/installation/after-installation/etcd-backup-and-restoration/_index.md b/content/rancher/v2.x/en/installation/after-installation/etcd-backup-and-restoration/_index.md index 05deef8c483..445f813e6b2 100644 --- a/content/rancher/v2.x/en/installation/after-installation/etcd-backup-and-restoration/_index.md +++ b/content/rancher/v2.x/en/installation/after-installation/etcd-backup-and-restoration/_index.md @@ -1,7 +1,6 @@ --- title: Etcd Snapshots weight: 370 -draft: true --- You can configure a Rancher Kubernetes Engine (RKE) cluster to automatically take snapshots of etcd. In a disaster scenario, you can restore these snapshots, which are stored on other cluster nodes. @@ -9,10 +8,10 @@ You can configure a Rancher Kubernetes Engine (RKE) cluster to automatically tak RKE introduce a new command that can take a snapshot of a running etcd node in rke cluster, the snapshot will be automatically saved in `/opt/rke/etcd-snapshots`, the commands works as following: ``` -./rke etcd snapshot-save --config cluster.yml +./rke etcd snapshot-save --config cluster.yml WARN[0000] Name of the snapshot is not specified using [rke_etcd_snapshot_2018-05-17T23:32:08+02:00] -INFO[0000] Starting saving snapshot on etcd hosts +INFO[0000] Starting saving snapshot on etcd hosts INFO[0000] [dialer] Setup tunnel for host [x.x.x.x] INFO[0001] [dialer] Setup tunnel for host [y.y.y.y] INFO[0002] [dialer] Setup tunnel for host [z.z.z.z] @@ -203,7 +202,7 @@ rke up --config cluster.yml ``` You can make sure that operations have been restored by checking the nginx deployment we created earlier: ``` -> kubectl get pods +> kubectl get pods NAME READY STATUS RESTARTS AGE nginx-65899c769f-kcdpr 1/1 Running 0 17s nginx-65899c769f-pc45c 1/1 Running 0 17s diff --git a/content/rancher/v2.x/en/upgrades/_index.md b/content/rancher/v2.x/en/upgrades/_index.md index c9da97aa83e..b688f8d49cc 100644 --- a/content/rancher/v2.x/en/upgrades/_index.md +++ b/content/rancher/v2.x/en/upgrades/_index.md @@ -1,7 +1,6 @@ --- title: Upgrades weight: 1000 -draft: true --- This section includes instructions for upgrading Rancher from previous versions. diff --git a/content/rancher/v2.x/en/upgrades/ha-server-upgrade/_index.md b/content/rancher/v2.x/en/upgrades/ha-server-upgrade/_index.md index 646116798d7..84e371ec357 100644 --- a/content/rancher/v2.x/en/upgrades/ha-server-upgrade/_index.md +++ b/content/rancher/v2.x/en/upgrades/ha-server-upgrade/_index.md @@ -1,7 +1,6 @@ --- title: High Availability Upgrade weight: 1020 -draft: true --- To upgrade Rancher 2.x running in a high availablity configuration, run an upgrade command that points to your upgrade config file. @@ -13,12 +12,12 @@ To upgrade Rancher 2.x running in a high availablity configuration, run an upgra 1. From your workstation, open **Terminal**. -2. Enter the following command: +2. Enter the ng command: ``` kubectl --kubeconfig=kube_config-rancher-cluster.yml set image deployment/cattle cattle-server=rancher/rancher: -n cattle-system ``` - Replace `` with the version that you want to upgrade to. For a list of tags available, see [DockerHub](https://hub.docker.com/r/rancher/rancher/tags/). + Replace `` with the version that you want to upgrade to. For a list of tags available, see [DockerHub](https://hub.docker.com/r/rancher/rancher/tags/). However, don't use any tag suffixed with `-rc`, as they are used for testing and are not officially supported. **Step Result:** The upgrade begins. Rancher Server may be unavailable for a few minutes. diff --git a/content/rancher/v2.x/en/upgrades/single-node-upgrade/_index.md b/content/rancher/v2.x/en/upgrades/single-node-upgrade/_index.md index c082e606fa0..eb13a6011ce 100644 --- a/content/rancher/v2.x/en/upgrades/single-node-upgrade/_index.md +++ b/content/rancher/v2.x/en/upgrades/single-node-upgrade/_index.md @@ -1,7 +1,6 @@ --- title: Single Node Upgrade weight: 1010 -draft: true --- To upgrade Rancher Server 2.x to the latest version, you need to enter only a few commands. @@ -18,7 +17,7 @@ docker stop 2. Create a `rancher-data` container. This container backs up the data from your current Rancher Server, which you'll restore in step 4. - Replace `` with the same ID from the previous step. - - Replace `` with the version of Rancher that you are currently running, as mentioned in the **Rrerequisite** above. + - Replace `` with the version of Rancher that you are currently running, as mentioned in the **Prerequisite** above. ``` docker create --volumes-from \ @@ -28,11 +27,9 @@ docker create --volumes-from \ 3. Pull the most recent image of Rancher. ``` -docker pull rancher/rancher: +docker pull rancher/rancher:latest ``` - Replace `` with the version that you want to upgrade to. For a list of tags available, see [DockerHub](https://hub.docker.com/r/rancher/rancher/tags/). - 4. Launch a new Rancher Server container using the `rancher-data` container. ```