public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-05-26 14:48:30 +00:00
Code Issues Packages Projects Releases Wiki Activity

making corrections per Seb

Browse Source
This commit is contained in:
Mark Bishop
2018-10-25 15:10:24 -07:00
parent 0473937df6
commit e15cdd1774
2 changed files with 7 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.x/en/upgrades/upgrades/ha-server-upgrade-helm/_index.md
+3 -3
View File
@@ -35,7 +35,7 @@ The following instructions will guide you through upgrading a high-availability
helm init --upgrade --service-account tiller
```
- **Upgrades to v2.0.7+ only: check system namespace locations**
Starting in v2.0.7, Rancher introduced the `system` project, which is a project that's automatically created to store important namespaces that Kubernetes needs to operate. During upgrade to v2.0.7+, Rancher expects these namespaces to be unassigned from all projects. Before beginning upgrade, check your system namespaces to make sure that they're unassigned to [prevent cluster networking issues]({{< baseurl >}}/rancher/v2.x/en/upgrades/upgrades/namespace-migration/#preventing-cluster-networking-issues).
Starting in v2.0.7, Rancher introduced the `System` project, which is a project that's automatically created to store important namespaces that Kubernetes needs to operate. During upgrade to v2.0.7+, Rancher expects these namespaces to be unassigned from all projects. Before beginning upgrade, check your system namespaces to make sure that they're unassigned to [prevent cluster networking issues]({{< baseurl >}}/rancher/v2.x/en/upgrades/upgrades/namespace-migration/#preventing-cluster-networking-issues).
## Upgrade Rancher
@@ -78,11 +78,11 @@ The following instructions will guide you through upgrading a high-availability
helm upgrade rancher rancher-<CHART_REPO>/rancher --set hostname=rancher.my.org
```
**Result:** Rancher is upgraded. Log back into Rancher to confirm that the upgrade succeeded.
**Result:** Rancher is upgraded. Log back into Rancher to confirm that the upgrade succeeded.
>**Having Network Issues Following Upgrade?**
>
> See [Restoring Cluster Networking]({{< baseurl >}}/rancher/v2.x/en/upgrades/upgrades/namespace-migration/#restoring-cluster-networking).
> See [Restoring Cluster Networking]({{< baseurl >}}/rancher/v2.x/en/upgrades/upgrades/namespace-migration/#restoring-cluster-networking).
## Rolling Back
content/rancher/v2.x/en/upgrades/upgrades/namespace-migration/_index.md
+4 -3
View File
@@ -72,14 +72,15 @@ Reset the cluster nodes' network policies to restore connectivity.
1. Before repairing networking, run the following two commands to make sure that your nodes have a status of `Ready` and that your cluster components are `Healthy`.
```
kubectl get nodes
kubectl get nodes --kubeconfig kube_config_rancher-cluster.yml
NAME STATUS ROLES AGE VERSION
165.227.114.63 Ready controlplane,etcd,worker 11m v1.10.1
165.227.116.167 Ready controlplane,etcd,worker 11m v1.10.1
165.227.127.226 Ready controlplane,etcd,worker 11m v1.10.1
kubectl get cs
kubectl get cs --kubeconfig kube_config_rancher-cluster.yml
NAME STATUS MESSAGE ERROR
scheduler Healthy ok
controller-manager Healthy ok
@@ -115,7 +116,7 @@ Reset the cluster nodes' network policies to restore connectivity.
c-59ptz custom false
local local false
1. Now remove all `networkpolicies` from system namespaces. Run this command for each cluster, using the kubeconfig generated by RKE.
1. Now remove all network policies from system namespaces. Run this command for each cluster, using the kubeconfig generated by RKE.
```
for namespace in kube-system kube-public cattle-system cattle-alerting cattle-logging cattle-pipeline ingress-nginx; do