mirror of
https://github.com/rancher/rancher-docs.git
synced 2026-05-22 04:45:19 +00:00
Correct 'available as of' versions
This commit is contained in:
@@ -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_
|
||||
_Available as of v2.4.0-alpha1_
|
||||
|
||||
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_
|
||||
_Available as of v2.4.0-alpha1_
|
||||
|
||||
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_
|
||||
_Available as of v2.4.0-alpha1_
|
||||
|
||||
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_
|
||||
_Available as of v2.4.0-alpha1_
|
||||
|
||||
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.
|
||||
|
||||
|
||||
@@ -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, 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-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.
|
||||
|
||||
# Custom Global Permissions
|
||||
|
||||
|
||||
@@ -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_
|
||||
_Available as of v2.4.0-alpha1_
|
||||
|
||||
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.
|
||||
|
||||
|
||||
@@ -3,7 +3,7 @@ title: Security Scans
|
||||
weight: 1
|
||||
---
|
||||
|
||||
_Available as of v2.4_
|
||||
_Available as of v2.4.0-alpha1_
|
||||
|
||||
Rancher can 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.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user