diff --git a/.gitbook/assets/2.40.0-RBAC-policy-configuration.png b/.gitbook/assets/2.40.0-RBAC-policy-configuration.png new file mode 100644 index 00000000..5bd872d2 Binary files /dev/null and b/.gitbook/assets/2.40.0-RBAC-policy-configuration.png differ diff --git a/.gitbook/assets/2.40.0-kube-RBAC-config.png b/.gitbook/assets/2.40.0-kube-RBAC-config.png new file mode 100644 index 00000000..bfdd98f4 Binary files /dev/null and b/.gitbook/assets/2.40.0-kube-RBAC-config.png differ diff --git a/.gitbook/assets/2.40.0-kube-registry-policy.png b/.gitbook/assets/2.40.0-kube-registry-policy.png new file mode 100644 index 00000000..41694e8b Binary files /dev/null and b/.gitbook/assets/2.40.0-kube-registry-policy.png differ diff --git a/.gitbook/assets/2.40.0-registry-policy-configuration.png b/.gitbook/assets/2.40.0-registry-policy-configuration.png new file mode 100644 index 00000000..0469dc6a Binary files /dev/null and b/.gitbook/assets/2.40.0-registry-policy-configuration.png differ diff --git a/admin/environments/policies/docker-policies/rbac-policy.md b/admin/environments/policies/docker-policies/rbac-policy.md index 7551a5bd..e565dbd7 100644 --- a/admin/environments/policies/docker-policies/rbac-policy.md +++ b/admin/environments/policies/docker-policies/rbac-policy.md @@ -22,6 +22,6 @@ Currently, only custom RBAC policies can be created. Future improvements to the | Users/teams | Select one or more [users](../../../user/users.md) or [teams](../../../user/teams/) from the dropdown menu. | | Role | Select the role you want to assign to the users or teams. | -
+
Click **Add Access** to add the user/team to the policy, multiple users or teams can be added. Each access added will show in the **Access list**. When you have finished adding access, click **Create policy**. A confirmation screen displays the changes being made and any existing policy that will be replaced. Click **Confirm** to acknowledge the changes and create the policy. diff --git a/admin/environments/policies/docker-policies/registry-policy.md b/admin/environments/policies/docker-policies/registry-policy.md index b4c7480a..12e2f9a2 100644 --- a/admin/environments/policies/docker-policies/registry-policy.md +++ b/admin/environments/policies/docker-policies/registry-policy.md @@ -22,6 +22,6 @@ Currently, only custom registry policies can be created. Future improvements to | Select registry | ​Select a [registry](../../../../user/kubernetes/cluster/registries.md) from the dropdown menu. ​ | | Select users and/or teams | Select one or more [user](../../../user/users.md) or [team](../../../user/teams/) that you want to have access to the selected registry. | -
+
Click **Add Access** to add the registry to the access list, multiple entries can be added. Each access added will show in the **Registry access list**. When you have finished adding access, click **Create policy**. A confirmation screen displays the changes being made and any existing policy that will be replaced. Click **Confirm** to acknowledge the changes and create the policy. diff --git a/admin/environments/policies/kubernetes-policies/kubernetes-rbac-policy.md b/admin/environments/policies/kubernetes-policies/kubernetes-rbac-policy.md index 03a2aa14..06cf8213 100644 --- a/admin/environments/policies/kubernetes-policies/kubernetes-rbac-policy.md +++ b/admin/environments/policies/kubernetes-policies/kubernetes-rbac-policy.md @@ -22,6 +22,6 @@ Currently, only custom RBAC policies can be created. Future improvements to the | Users/teams | Select one or more [users](../../../user/users.md) or [teams](../../../user/teams/) from the dropdown menu. | | Role |

Select the role you want to assign to the users or teams.
If you select a namespace-scoped role, a Namespaces field will appear, allowing you to pick one or more existing namespaces, or to type a name to add a new namespace.

| -
+
Click **Add Access** to add a user or team to the policy. You can add multiple users or teams, and each entry appears in the **Access list**. When you have finished adding access, click **Create policy**. A confirmation screen displays the changes being made and any existing policy that will be replaced. Click **Confirm** to acknowledge the changes and create the policy. diff --git a/admin/environments/policies/kubernetes-policies/kubernetes-registry-policy.md b/admin/environments/policies/kubernetes-policies/kubernetes-registry-policy.md index df9593ac..b39889b1 100644 --- a/admin/environments/policies/kubernetes-policies/kubernetes-registry-policy.md +++ b/admin/environments/policies/kubernetes-policies/kubernetes-registry-policy.md @@ -45,7 +45,7 @@ The **Allowed sources** list is pre-populated with common images, including thos | Registry URL prefix |

The container image or registry that is permitted for deployment.

Enter the registry hostname and optional path prefix. Only images whose fully-qualified reference starts with this prefix will be allowed.

| | Scope | Specify whether the allowed access should apply cluster-wide (Global) or be restricted to selected [namespaces](../../../../user/kubernetes/namespaces/) only. | -
+
Click **Add source** to add an image to the allowed sources list. You can add multiple entries, and each will appear in the **Allowed sources** table. To remove a source, select the checkbox next to the entry and click **Remove** in the top right corner of the table.