GITBOOK-24: C9S-58 - Policy access list changes

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.                                                                                                                                                                 |
 
-<figure><img src="../../../../.gitbook/assets/2.37-RBAC-policy.png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../../../.gitbook/assets/2.40.0-RBAC-policy-configuration.png" alt=""><figcaption></figcaption></figure>
 
 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.

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.                                                                                  |
 
-<figure><img src="../../../../.gitbook/assets/2.37-docker-registry.png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../../../.gitbook/assets/2.40.0-registry-policy-configuration.png" alt=""><figcaption></figcaption></figure>
 
 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.

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               | <p>Select the role you want to assign to the users or teams. <br>If you select a <a href="../../../../user/kubernetes/namespaces/">namespace-scoped role</a>, a <strong>Namespaces</strong> field will appear, allowing you to pick one or more existing namespaces, or to type a name to add a new namespace.</p> |
 
-<figure><img src="../../../../.gitbook/assets/2.37.0-Kube-RBAC-example.png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../../../.gitbook/assets/2.40.0-kube-RBAC-config.png" alt=""><figcaption></figcaption></figure>
 
 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.

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 | <p>The container image or <a href="../../../../user/docker/host/registries.md">registry</a> that is permitted for deployment. </p><p>Enter the registry hostname and optional path prefix. Only images whose fully-qualified reference starts with this prefix will be allowed.</p> |
 | Scope               | Specify whether the allowed access should apply cluster-wide (Global) or be restricted to selected [namespaces](../../../../user/kubernetes/namespaces/) only.                                                                                                                      |
 
-<figure><img src="../../../../.gitbook/assets/2.39-container-image-restrictions.png" alt=""><figcaption></figcaption></figure>
+<figure><img src="../../../../.gitbook/assets/2.40.0-kube-registry-policy.png" alt=""><figcaption></figcaption></figure>
 
 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.