From 9abbc87d6687ad10f39a83dd1a0d6defaf1cdaa3 Mon Sep 17 00:00:00 2001 From: dnoland1 Date: Thu, 4 Apr 2019 14:20:57 -0700 Subject: [PATCH 01/33] Update _index.md --- content/rke/latest/en/config-options/services/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rke/latest/en/config-options/services/_index.md b/content/rke/latest/en/config-options/services/_index.md index 3094ce25381..6fb743534f6 100644 --- a/content/rke/latest/en/config-options/services/_index.md +++ b/content/rke/latest/en/config-options/services/_index.md @@ -65,7 +65,7 @@ services: ### Kubernetes Controller Manager Options -RKE support the following options for the `kube-controller` service: +RKE supports the following options for the `kube-controller` service: - **Cluster CIDR** (`cluster_cidr`) - The CIDR pool used to assign IP addresses to pods in the cluster. By default, each node in the cluster is assigned a `/24` network from this pool for pod IP assignments. The default value for this option is `10.42.0.0/16`. - **Service Cluster IP Range** (`service_cluster_ip_range`) - This is the virtual IP address that will be assigned to services created on Kubernetes. By default, the service cluster IP range is `10.43.0.0/16`. If you change this value, then it must also be set with the same value on the Kubernetes API server (`kube-api`). From c1242037222801af1d649268e14b8a56a547abf3 Mon Sep 17 00:00:00 2001 From: dnoland1 Date: Thu, 4 Apr 2019 15:49:36 -0700 Subject: [PATCH 02/33] Update _index.md --- content/rancher/v2.x/en/cluster-admin/backing-up-etcd/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.x/en/cluster-admin/backing-up-etcd/_index.md b/content/rancher/v2.x/en/cluster-admin/backing-up-etcd/_index.md index 4b598cf59cf..19eaa115c2b 100644 --- a/content/rancher/v2.x/en/cluster-admin/backing-up-etcd/_index.md +++ b/content/rancher/v2.x/en/cluster-admin/backing-up-etcd/_index.md @@ -9,7 +9,7 @@ In the Rancher UI, etcd backup and recovery for [Rancher launched Kubernetes clu Rancher recommends enabling the ability to set up recurring snapshots, but one-time snapshots can easily be taken as well. ->**Note:** If you have any Rancher launched Kubernetes clusters that were created prior to v2.2.0, after upgrading Ranchher, you must [edit the cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/editing-clusters/) and _save_ it, in order to enable the updated snapshot features. Even if you were already creating snapshots prior to v2.2.0, you must do this step as the older snapshots will not be available to use to [back up and restore etcd through the UI]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/restoring-etcd/). +>**Note:** If you have any Rancher launched Kubernetes clusters that were created prior to v2.2.0, after upgrading Rancher, you must [edit the cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/editing-clusters/) and _save_ it, in order to enable the updated snapshot features. Even if you were already creating snapshots prior to v2.2.0, you must do this step as the older snapshots will not be available to use to [back up and restore etcd through the UI]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/restoring-etcd/). ## Configuring Recurring Snapshots for the Cluster From b99100a3be810a7bcbdb1d6999d2850f50980bfc Mon Sep 17 00:00:00 2001 From: David Noland Date: Thu, 4 Apr 2019 15:53:19 -0700 Subject: [PATCH 03/33] Another Ranchher typo --- content/rancher/v2.x/en/cluster-admin/restoring-etcd/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.x/en/cluster-admin/restoring-etcd/_index.md b/content/rancher/v2.x/en/cluster-admin/restoring-etcd/_index.md index 95146d16814..e79f9f20478 100644 --- a/content/rancher/v2.x/en/cluster-admin/restoring-etcd/_index.md +++ b/content/rancher/v2.x/en/cluster-admin/restoring-etcd/_index.md @@ -9,7 +9,7 @@ etcd backup and recovery for [Rancher launched Kubernetes clusters]({{< baseurl Rancher recommends enabling the [ability to set up recurring snapshots of etcd]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/backing-up-etcd/#configuring-recurring-snapshots-for-the-cluster), but [one-time snapshots]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/backing-up-etcd/#one-time-snapshots) can easily be taken as well. Rancher allows restore from [saved snapshots](#restoring-your-cluster-from-a-snapshot) or if you don't have any snapshots, you can still [restore etcd](#recovering-etcd-without-a-snapshot). ->**Note:** If you have any Rancher launched Kubernetes clusters that were created prior to v2.2.0, after upgrading Ranchher, you must [edit the cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/editing-clusters/) and _save_ it, in order to enable the [updated snapshot features]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/backing-up-etcd/). Even if you were already creating snapshots prior to v2.2.0, you must do this step as the older snapshots will not be available to use to back up and restore etcd through the UI. +>**Note:** If you have any Rancher launched Kubernetes clusters that were created prior to v2.2.0, after upgrading Rancher, you must [edit the cluster]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/editing-clusters/) and _save_ it, in order to enable the [updated snapshot features]({{< baseurl >}}/rancher/v2.x/en/cluster-admin/backing-up-etcd/). Even if you were already creating snapshots prior to v2.2.0, you must do this step as the older snapshots will not be available to use to back up and restore etcd through the UI. ## Viewing Available Snapshots From e8fa5cdd331d2fe3936dcd3f3724f1724047852d Mon Sep 17 00:00:00 2001 From: Sebastiaan van Steenis Date: Thu, 4 Apr 2019 14:26:20 +0200 Subject: [PATCH 04/33] Add Rancher leader election to troubleshooting --- .../v2.x/en/troubleshooting/rancherha/_index.md | 10 ++++++++++ 1 file changed, 10 insertions(+) diff --git a/content/rancher/v2.x/en/troubleshooting/rancherha/_index.md b/content/rancher/v2.x/en/troubleshooting/rancherha/_index.md index 9ef9d9e0d99..5a90616e985 100644 --- a/content/rancher/v2.x/en/troubleshooting/rancherha/_index.md +++ b/content/rancher/v2.x/en/troubleshooting/rancherha/_index.md @@ -68,3 +68,13 @@ When accessing your configured Rancher FQDN does not show you the UI, check the ``` kubectl -n ingress-nginx logs -l app=ingress-nginx ``` + +### Leader election + +The leader is determined by a leader election process. After the leader has been determined, the leader (`holderIdentity`) is saved in the `cattle-controllers` ConfigMap (in this example, `rancher-7dbd7875f7-qbj5k`). + +``` +kubectl -n kube-system get configmap cattle-controllers -o jsonpath='{.metadata.annotations.control-plane\.alpha\.kubernetes\.io/leader}' +{"holderIdentity":"rancher-7dbd7875f7-qbj5k","leaseDurationSeconds":45,"acquireTime":"2019-04-04T11:53:12Z","renewTime":"2019-04-04T12:24:08Z","leaderTransitions":0} +``` + From c98a19607da4cf99de793c656a6e3d3ce97fa9b1 Mon Sep 17 00:00:00 2001 From: dnoland1 Date: Wed, 3 Apr 2019 13:54:28 -0700 Subject: [PATCH 05/33] Update _index.md --- content/rke/latest/en/installation/_index.md | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+) diff --git a/content/rke/latest/en/installation/_index.md b/content/rke/latest/en/installation/_index.md index 5fd20634b65..738f294a5ab 100644 --- a/content/rke/latest/en/installation/_index.md +++ b/content/rke/latest/en/installation/_index.md @@ -6,6 +6,7 @@ weight: 50 RKE is a fast, versatile Kubernetes installer that you can use to install Kubernetes on your Linux hosts. You can get started in a couple of quick and easy steps: 1. [Download the RKE Binary](#download-the-rke-binary) + 1. [Alternative RKE MacOS X Install - Homebrew](#alternative-rke-macos-x-install---homebrew) 1. [Prepare the Nodes for the Kubernetes Cluster](#prepare-the-nodes-for-the-kubernetes-cluster) 1. [Creating the Cluster Configuration File](#creating-the-cluster-configuration-file) 1. [Deploying Kubernetes with RKE](#deploying-kubernetes-with-rke) @@ -49,6 +50,25 @@ RKE is a fast, versatile Kubernetes installer that you can use to install Kubern $ rke --version ``` + +### Alternative RKE MacOS X Install - Homebrew + +RKE can also be installed and updated using Homebrew, a package manager for MacOS X. + +1. Install Homebrew. See https://brew.sh/ for instructions. + +2. Using `brew`, install RKE by running the following command in a Terminal window: + + ``` + $ brew install rke + ``` + +If you have already installed RKE using `brew`, you can upgrade RKE by running: + +``` +$ brew upgrade rke +``` + ## Prepare the Nodes for the Kubernetes cluster The Kubernetes cluster components are launched using Docker on a Linux distro. You can use any Linux you want, as long as you can install Docker on it. From cc730cabfcb8baa466761b8c274aa094defbb901 Mon Sep 17 00:00:00 2001 From: dnoland1 Date: Fri, 5 Apr 2019 11:41:49 -0700 Subject: [PATCH 06/33] Update _index.md --- .../cleaning-cluster-nodes/_index.md | 16 ++++++++-------- 1 file changed, 8 insertions(+), 8 deletions(-) diff --git a/content/rancher/v2.x/en/cluster-admin/cleaning-cluster-nodes/_index.md b/content/rancher/v2.x/en/cluster-admin/cleaning-cluster-nodes/_index.md index 5140e780a9a..e30565da8e0 100644 --- a/content/rancher/v2.x/en/cluster-admin/cleaning-cluster-nodes/_index.md +++ b/content/rancher/v2.x/en/cluster-admin/cleaning-cluster-nodes/_index.md @@ -19,16 +19,16 @@ When cleaning nodes provisioned using Rancher, the following components are dele | `serviceAccount`, `clusterRoles`, and `clusterRoleBindings` labeled by Rancher | ✓ | ✓ | ✓ | ✓ | | Labels, Annotations, and Finalizers | ✓ | ✓ | ✓ | ✓ | | Rancher Deployment | ✓ | ✓ | ✓ | | -| Machines, clusters, projects, and user custom resource deployments (CRDs) | ✓ | ✓ | ✓ | | +| Machines, clusters, projects, and user custom resource defintions (CRDs) | ✓ | ✓ | ✓ | | | All resources create under the `management.cattle.io` API Group | ✓ | ✓ | ✓ | | -| All CRDs created by Rancher v2.0.x | ✓ | ✓ | ✓ | | +| All CRDs created by Rancher v2.x | ✓ | ✓ | ✓ | | [1]: {{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/node-pools/ [2]: {{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/rke-clusters/custom-nodes/ [3]: {{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/hosted-kubernetes-clusters/ [4]: {{< baseurl >}}/rancher/v2.x/en/cluster-provisioning/imported-clusters/ -## Removing A Node from a Cluster by Rancher UI +## Removing a Node from a Cluster by Rancher UI When the node is in `Active` state, removing the node from a cluster will trigger a process to clean up the node. Please restart the node after the automatic cleanup process is done to make sure any non-persistent data is properly removed. @@ -36,10 +36,10 @@ When the node is in `Active` state, removing the node from a cluster will trigge ``` # using reboot -reboot +$ sudo reboot # using shutdown -shutdown -r now +$ sudo shutdown -r now ``` ## Cleaning a Node Manually @@ -183,10 +183,10 @@ The remaining two components that are changed/configured are (virtual) network i ``` # using reboot -reboot +$ sudo reboot # using shutdown -shutdown -r now +$ sudo shutdown -r now ``` If you want to know more on (virtual) network interfaces or iptables rules, please see the specific subjects below. @@ -223,7 +223,7 @@ ip link delete interface_name >**Note:** Depending on the network provider configured for the cluster the node was part of, some of the chains will or won't be present on the node. -Iptables rules are used to route traffic from and to containers. The created rules are not persistent, so restarting the node will restore iptables to it's original state. +Iptables rules are used to route traffic from and to containers. The created rules are not persistent, so restarting the node will restore iptables to its original state. Chains | --------| From fd22e4f9060f1cfe2a5a13a1dfd56bf47a08dbaa Mon Sep 17 00:00:00 2001 From: David Noland Date: Fri, 5 Apr 2019 11:45:42 -0700 Subject: [PATCH 07/33] Fixed typo --- .../v2.x/en/cluster-admin/cleaning-cluster-nodes/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.x/en/cluster-admin/cleaning-cluster-nodes/_index.md b/content/rancher/v2.x/en/cluster-admin/cleaning-cluster-nodes/_index.md index e30565da8e0..3d0ede984a5 100644 --- a/content/rancher/v2.x/en/cluster-admin/cleaning-cluster-nodes/_index.md +++ b/content/rancher/v2.x/en/cluster-admin/cleaning-cluster-nodes/_index.md @@ -19,7 +19,7 @@ When cleaning nodes provisioned using Rancher, the following components are dele | `serviceAccount`, `clusterRoles`, and `clusterRoleBindings` labeled by Rancher | ✓ | ✓ | ✓ | ✓ | | Labels, Annotations, and Finalizers | ✓ | ✓ | ✓ | ✓ | | Rancher Deployment | ✓ | ✓ | ✓ | | -| Machines, clusters, projects, and user custom resource defintions (CRDs) | ✓ | ✓ | ✓ | | +| Machines, clusters, projects, and user custom resource definitions (CRDs) | ✓ | ✓ | ✓ | | | All resources create under the `management.cattle.io` API Group | ✓ | ✓ | ✓ | | | All CRDs created by Rancher v2.x | ✓ | ✓ | ✓ | | From 36bbb43f877ad01f5f89d2e55578966336c19664 Mon Sep 17 00:00:00 2001 From: dnoland1 Date: Sat, 6 Apr 2019 19:54:33 -0700 Subject: [PATCH 08/33] Update _index.md --- content/rancher/v2.x/en/project-admin/resource-quotas/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.x/en/project-admin/resource-quotas/_index.md b/content/rancher/v2.x/en/project-admin/resource-quotas/_index.md index b2f98bc7065..150463f4a8c 100644 --- a/content/rancher/v2.x/en/project-admin/resource-quotas/_index.md +++ b/content/rancher/v2.x/en/project-admin/resource-quotas/_index.md @@ -20,7 +20,7 @@ In the following diagram, a Kubernetes admin is trying to enforce a resource quo Base Kubernetes: Unique Resource Quotas Being Applied to Each Namespace ![Native Kubernetes Resource Quota Implementation]({{< baseurl >}}/img/rancher/kubernetes-resource-quota.svg) -Resource quotas are a little different in Rancher. In Rancher, you apply a resource quota to the [project]({{< baseurl >}}/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/#projects), and then the quota propagates to each namespace, whereafter Kubernetes enforces you limits using the native version of resource quotas. If you want to change the quota for a specific namespace, you can [override it](#overriding-the-default-limit-for-a-namespace). +Resource quotas are a little different in Rancher. In Rancher, you apply a resource quota to the [project]({{< baseurl >}}/rancher/v2.x/en/k8s-in-rancher/projects-and-namespaces/#projects), and then the quota propagates to each namespace, whereafter Kubernetes enforces your limits using the native version of resource quotas. If you want to change the quota for a specific namespace, you can [override it](#overriding-the-default-limit-for-a-namespace). The resource quota includes two limits, which you set while creating or editing a project: From 418eb528b78211756b8ff78eede0d9285017d67f Mon Sep 17 00:00:00 2001 From: dnoland1 Date: Fri, 5 Apr 2019 23:31:06 -0700 Subject: [PATCH 09/33] Update _index.md --- .../v2.x/en/installation/ha/kubernetes-rke/_index.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) diff --git a/content/rancher/v2.x/en/installation/ha/kubernetes-rke/_index.md b/content/rancher/v2.x/en/installation/ha/kubernetes-rke/_index.md index 05f5ed1e839..88dbcb7e8f9 100644 --- a/content/rancher/v2.x/en/installation/ha/kubernetes-rke/_index.md +++ b/content/rancher/v2.x/en/installation/ha/kubernetes-rke/_index.md @@ -78,9 +78,9 @@ Test your connectivity with `kubectl` and see if all your nodes are in `Ready` s kubectl get nodes 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 +165.227.114.63 Ready controlplane,etcd,worker 11m v1.13.5 +165.227.116.167 Ready controlplane,etcd,worker 11m v1.13.5 +165.227.127.226 Ready controlplane,etcd,worker 11m v1.13.5 ``` ### Check the Health of Your Cluster Pods From 66aa35c36a52eb21ba4705e36e95a4744d0b4267 Mon Sep 17 00:00:00 2001 From: Denise Schannon Date: Thu, 11 Apr 2019 14:40:13 -0700 Subject: [PATCH 10/33] upate broken link --- content/rancher/v2.x/en/catalog/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/rancher/v2.x/en/catalog/_index.md b/content/rancher/v2.x/en/catalog/_index.md index 57d577713a2..ec079814f6c 100644 --- a/content/rancher/v2.x/en/catalog/_index.md +++ b/content/rancher/v2.x/en/catalog/_index.md @@ -75,7 +75,7 @@ _Available as of v2.2.0_ In Rancher v2.2.0, you can add private catalog repositories using credentials like Username and Password. You may also want to use the OAuth token if your Git or Helm repository server support that. -[Read More About Adding Private Git/Helm Catalogs]({{< baseurl >}}/rancher/v2.x/en/catalog/private/) +[Read More About Adding Private Git/Helm Catalogs]({{< baseurl >}}/rancher/v2.x/en/catalog/custom/#private-repositories)