public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-05-25 06:08:29 +00:00
Code Issues Packages Projects Releases Wiki Activity

Created new section for project-scoped registries in UI

Browse Source
This commit is contained in:
Jennifer Travinski
2021-11-16 11:22:05 -05:00
parent ecd9f73932
commit 5263e25c98
1 changed files with 19 additions and 2 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/rancher/v2.6/en/k8s-in-rancher/registries/_index.md
+19 -2
View File
@@ -14,13 +14,13 @@ Deployments use the Kubernetes registry secret to authenticate with a private Do
Currently, deployments pull the private registry credentials automatically only if the workload is created in the Rancher UI and not when it is created via kubectl.
# Creating a Registry
# Creating a Registry in Namespaces
>**Prerequisites:** You must have a [private registry](https://docs.docker.com/registry/deploying/) available to use.
1. In the upper left corner, click **☰ > Cluster Management**.
1. Go to the cluster where you want to add a registry and click **Explore**.
1. In the left navigation lick **More Resources > Core > Secrets**.
1. In the left navigation, click either **Storage > Secrets** or **More Resources > Core > Secrets**.
1. Click **Create**.
1. Click **Registry**.
1. Enter a **Name** for the registry.
@@ -39,6 +39,23 @@ Currently, deployments pull the private registry credentials automatically only
- You can view the secret in the Rancher UI from the **Resources > Registries** view.
- Any workload that you create in the Rancher UI will have the credentials to access the registry if the workload is within the registry's scope.
# Creating a Registry in Projects
>**Prerequisites:** You must have a [private registry](https://docs.docker.com/registry/deploying/) available to use.
Prior to v2.6, secrets were required to be in a project scope. Projects are no longer required, and you may use the namespace scope instead. As a result, the Rancher UI was updated to reflect this new functionality. However, you may still create a project-scoped registry if desired. Use the following steps to do so:
1. In the upper left corner, click **☰ > Global Settings** in the dropdown.
1. Click **Feature Flags**.
1. Go to the `legacy` feature flag and click **Activate**.
1. Continue following [steps 1 - 9]({{<baseurl>}}/rancher/v2.6/en/k8s-in-rancher/registries/#creating-a-registry-in-namespaces) above to create and save your project-level registry. Note that in Step 7 above, you will select the project rather than the namespace you want to use.
**Result:**
- Your secret is added to the project you chose.
- You can view the secret in the Rancher UI from the **Resources > Registries** view.
- Any workload that you create in the Rancher UI will have the credentials to access the registry if the workload is within the registry's scope.
# Using a Private Registry
You can deploy a workload with an image from a private registry through the Rancher UI, or with `kubectl`.