From c0659b98cb76ba7ec902a758bbceb1524b894b84 Mon Sep 17 00:00:00 2001 From: Catherine Luse Date: Mon, 30 Mar 2020 13:25:54 -0700 Subject: [PATCH] Minor edits --- .../en/admin-settings/rbac/default-custom-roles/_index.md | 8 ++++---- .../en/admin-settings/rbac/global-permissions/_index.md | 4 ++-- content/rancher/v2.x/en/cluster-admin/tools/_index.md | 2 +- .../v2.x/en/cluster-admin/upgrading-kubernetes/_index.md | 2 +- content/rancher/v2.x/en/security/_index.md | 2 +- 5 files changed, 9 insertions(+), 9 deletions(-) diff --git a/content/rancher/v2.x/en/admin-settings/rbac/default-custom-roles/_index.md b/content/rancher/v2.x/en/admin-settings/rbac/default-custom-roles/_index.md index 61993bb082d..11c7bd0f80b 100644 --- a/content/rancher/v2.x/en/admin-settings/rbac/default-custom-roles/_index.md +++ b/content/rancher/v2.x/en/admin-settings/rbac/default-custom-roles/_index.md @@ -95,7 +95,7 @@ The steps to add custom roles differ depending on the version of Rancher. ## Creating a Custom Global Role that Copies Rules from an Existing Role -_Available as of v2.4.0-alpha1_ +_Available as of v2.4.0_ If you have a group of individuals that need the same level of access in Rancher, it can save time to create a custom global role in which all of the rules from another role, such as the administrator role, are copied into a new role. This allows you to only configure the variations between the existing role and the new role. @@ -112,7 +112,7 @@ To create a custom global role based on an existing role, ## Creating a Custom Global Role that Does Not Copy Rules from Another Role -_Available as of v2.4.0-alpha1_ +_Available as of v2.4.0_ Custom global roles don't have to be based on existing roles. To create a custom global role by choosing the specific Kubernetes resource operations that should be allowed for the role, follow these steps: @@ -125,7 +125,7 @@ Custom global roles don't have to be based on existing roles. To create a custom ## Deleting a Custom Global Role -_Available as of v2.4.0-alpha1_ +_Available as of v2.4.0_ When deleting a custom global role, all global role bindings with this custom role are deleted. @@ -141,7 +141,7 @@ To delete a custom global role, ## Assigning a Custom Global Role to a Group -_Available as of v2.4.0-alpha1_ +_Available as of v2.4.0_ If you have a group of individuals that need the same level of access in Rancher, it can save time to create a custom global role. When the role is assigned to a group, the users in the group have the appropriate level of access the first time they sign into Rancher. diff --git a/content/rancher/v2.x/en/admin-settings/rbac/global-permissions/_index.md b/content/rancher/v2.x/en/admin-settings/rbac/global-permissions/_index.md index 4f754a97d37..367d82bb81d 100644 --- a/content/rancher/v2.x/en/admin-settings/rbac/global-permissions/_index.md +++ b/content/rancher/v2.x/en/admin-settings/rbac/global-permissions/_index.md @@ -43,7 +43,7 @@ To see the default permissions for new users, go to the **Global** view and clic Permissions can be assigned to an individual user with [these steps.](#configuring-global-permissions-for-existing-individual-users) -As of Rancher v2.4.0-alpha1, you can [assign a role to everyone in the group at the same time](#configuring-global-permissions-for-groups) if the external authentication provider supports groups. +As of Rancher v2.4.0, you can [assign a role to everyone in the group at the same time](#configuring-global-permissions-for-groups) if the external authentication provider supports groups. # Custom Global Permissions @@ -128,7 +128,7 @@ To configure permission for a user, ### Configuring Global Permissions for Groups -_Available as of v2.4.0-alpha1_ +_Available as of v2.4.0_ If you have a group of individuals that need the same level of access in Rancher, it can save time to assign permissions to the entire group at once, so that the users in the group have the appropriate level of access the first time they sign into Rancher. diff --git a/content/rancher/v2.x/en/cluster-admin/tools/_index.md b/content/rancher/v2.x/en/cluster-admin/tools/_index.md index 9857ba5a641..ed8fd982157 100644 --- a/content/rancher/v2.x/en/cluster-admin/tools/_index.md +++ b/content/rancher/v2.x/en/cluster-admin/tools/_index.md @@ -13,7 +13,7 @@ Rancher contains a variety of tools that aren't included in Kubernetes to assist - [Logging](#logging) - [Monitoring](#monitoring) - [Istio](#istio) -- [OPA Gatekeeper](#opa) +- [OPA Gatekeeper](#opa-gatekeeper) diff --git a/content/rancher/v2.x/en/cluster-admin/upgrading-kubernetes/_index.md b/content/rancher/v2.x/en/cluster-admin/upgrading-kubernetes/_index.md index e2c44d9118d..a407c06af2b 100644 --- a/content/rancher/v2.x/en/cluster-admin/upgrading-kubernetes/_index.md +++ b/content/rancher/v2.x/en/cluster-admin/upgrading-kubernetes/_index.md @@ -83,7 +83,7 @@ The cluster cannot be downgraded to a previous Kubernetes version. **Result:** Kubernetes begins upgrading for the cluster. -# Rolling Back the Kubernetes Version +# Rolling Back _Available as of v2.4_ diff --git a/content/rancher/v2.x/en/security/_index.md b/content/rancher/v2.x/en/security/_index.md index 7cb5e2b4713..384657223f3 100644 --- a/content/rancher/v2.x/en/security/_index.md +++ b/content/rancher/v2.x/en/security/_index.md @@ -33,7 +33,7 @@ On this page, we provide security-related documentation along with resources to ### Running a CIS Security Scan on a Kubernetes Cluster -_Available as of v2.4.0-alpha1_ +_Available as of v2.4.0_ Rancher leverages [kube-bench](https://github.com/aquasecurity/kube-bench) to run a security scan to check whether Kubernetes is deployed according to security best practices as defined in the CIS (Center for Internet Security) Kubernetes Benchmark.