container registry > container image registry, removed slashes

2026-09-15 21:44:24 +00:00 · 2023-01-13 15:24:22 -05:00
parent 72e1f2d3b1
commit c5488da0c6
9 changed files with 37 additions and 41 deletions
@@ -2,7 +2,7 @@
 title: '1. Set up Infrastructure and Private Registry'
 ---

-In this section, you will provision the underlying infrastructure for your Rancher management server in an air gapped environment. You will also set up the private container registry that must be available to your Rancher node(s).
+In this section, you will provision the underlying infrastructure for your Rancher management server in an air gapped environment. You will also set up the private container image registry that must be available to your Rancher node(s).

 An air gapped environment is an environment where the Rancher server is installed offline or behind a firewall.

@@ -19,7 +19,7 @@ We recommend setting up the following infrastructure for a high-availability ins
 - **An external database** to store the cluster data. PostgreSQL, MySQL, and etcd are supported.
 - **A load balancer** to direct traffic to the two nodes.
 - **A DNS record** to map a URL to the load balancer. This will become the Rancher server URL, and downstream Kubernetes clusters will need to reach it.
- **A private container registry** to distribute container images to your machines.
+- **A private image registry** to distribute container images to your machines.

 ### 1. Set up Linux Nodes

@@ -78,7 +78,7 @@ You will need to specify this hostname in a later step when you install Rancher,

 For a how-to guide for setting up a DNS record to route domain traffic to an Amazon ELB load balancer, refer to the [official AWS documentation.](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-elb-load-balancer)

-### 5. Set up a Private Container Registry
+### 5. Set up a Private Image Registry

 Rancher supports air gap installs using a private registry. You must have your own private registry or other means of distributing container images to your machines.

@@ -98,7 +98,7 @@ To install the Rancher management server on a high-availability RKE cluster, we
 - **Three Linux nodes,** typically virtual machines, in an infrastructure provider such as Amazon's EC2, Google Compute Engine, or vSphere.
 - **A load balancer** to direct front-end traffic to the three nodes.
 - **A DNS record** to map a URL to the load balancer. This will become the Rancher server URL, and downstream Kubernetes clusters will need to reach it.
- **A private container registry** to distribute container images to your machines.
+- **A private image registry** to distribute container images to your machines.

 These nodes must be in the same region/data center. You may place these servers in separate availability zones.

@@ -149,7 +149,7 @@ You will need to specify this hostname in a later step when you install Rancher,

 For a how-to guide for setting up a DNS record to route domain traffic to an Amazon ELB load balancer, refer to the [official AWS documentation.](https://docs.aws.amazon.com/Route53/latest/DeveloperGuide/routing-to-elb-load-balancer)

-### 4. Set up a Private Container Registry
+### 4. Set up a Private Image Registry

 Rancher supports air gap installs using a secure private registry. You must have your own private registry or other means of distributing container images to your machines.

@@ -78,7 +78,7 @@ If you have an air gap setup, you might not be able to get the automatic periodi

 To sync Rancher with a local mirror of the RKE metadata, an administrator would configure the `rke-metadata-config` settings to point to the mirror. For details, refer to [Configuring the Metadata Synchronization.](#configuring-the-metadata-synchronization)

-After new Kubernetes versions are loaded into the Rancher setup, additional steps would be required in order to use them for launching clusters. Rancher needs access to updated system images. While the metadata settings can only be changed by administrators, any user can download the Rancher system images and prepare a private container registry for them.
+After new Kubernetes versions are loaded into the Rancher setup, additional steps would be required in order to use them for launching clusters. Rancher needs access to updated system images. While the metadata settings can only be changed by administrators, any user can download the Rancher system images and prepare a private container image registry for them.

 1. To download the system images for the private registry, click the Rancher server version at the bottom left corner of the Rancher UI.
 1. Download the OS specific image lists for Linux or Windows.
@@ -2,7 +2,7 @@
 title: Configuring a Global Default Private Registry
 ---

-You might want to use a private container registry to share your custom base images within your organization. With a private registry, you can keep a private, consistent, and centralized source of truth for the container images that are used in your clusters.
+You might want to use a private container image registry to share your custom base images within your organization. With a private registry, you can keep a private, consistent, and centralized source of truth for the container images that are used in your clusters.

 There are two main ways to set up private registries in Rancher: by setting up the global default registry through the **Settings** tab in the global view, and by setting up a private registry in the advanced options in the cluster-level settings. The global default registry is intended to be used for air-gapped setups, for registries that do not require credentials. The cluster-level private registry is intended to be used in all setups in which the private registry requires credentials.

@@ -1,15 +1,15 @@
 ---
-title: Kubernetes Registry and Container Registry
-description: Learn about the Container registry and Kubernetes registry, their use cases and how to use a private registry with the Rancher UI
+title: Kubernetes Registry and Container Image Registry
+description: Learn about the container image registry and Kubernetes registry, their use cases, and how to use a private registry with the Rancher UI
 ---
 Registries are Kubernetes secrets containing credentials used to authenticate with [private container registries](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/).

 The word "registry" can mean two things, depending on whether it is used to refer to a container or Kubernetes registry:

- A **Container registry** (formerly "Docker registry") contains container images that you can pull and deploy. The registry is a stateless, scalable server side application that stores and lets you distribute container images.
- The **Kubernetes registry** is an image pull secret that your deployment uses to authenticate with a container registry.
+- A **Container image registry** (formerly "Docker registry") contains container images that you can pull and deploy. The registry is a stateless, scalable server side application that stores and lets you distribute container images.
+- The **Kubernetes registry** is an image pull secret that your deployment uses to authenticate with an image registry.

-Deployments use the Kubernetes registry secret to authenticate with a private container registry and then pull a container image hosted on it.
+Deployments use the Kubernetes registry secret to authenticate with a private image registry and then pull a container image hosted on it.

 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.

@@ -143,22 +143,22 @@ In this example, the secret named `testquay` is in the default namespace.

 You can use `kubectl` to create the secret with the private registry credentials. This command creates the secret named `testquay`:

-// ```
-// kubectl create secret docker-registry testquay \
-//     --docker-server=quay.io \
-//     --docker-username=<Profile name> \
-//     --docker-password=<password>
-// ```
+```
+kubectl create secret docker-registry testquay \
+    --docker-server=quay.io \
+    --docker-username=<Profile name> \
+    --docker-password=<password>
+```

-// Need generic instructions
+Need generic instructions

 To see how the secret is stored in Kubernetes, you can use this command:

-// ```
-// kubectl get secret testquay --output="jsonpath={.data.\.dockerconfigjson}" | base64 --decode
-// ```
+```
+kubectl get secret testquay --output="jsonpath={.data.\.dockerconfigjson}" | base64 --decode
+```

-// Need generic instructions
+Need generic instructions

 The result looks like this:

@@ -8,7 +8,7 @@ RKE1 and RKE2 have several slight behavioral differences to note, and this page

 ### Control Plane Components

-RKE1 uses Docker for deploying and managing control plane components, and it also uses Docker as the container runtime for Kubernetes. By contrast, RKE2 launches control plane components as static pods that are managed by the kubelet. RKE2's container runtime is containerd, which allows things such as container registry mirroring (RKE1 with Docker does not).
+RKE1 uses Docker for deploying and managing control plane components, and it also uses Docker as the container runtime for Kubernetes. By contrast, RKE2 launches control plane components as static pods that are managed by the kubelet. RKE2's container runtime is containerd, which allows things such as mirroring a container image registry. RKE1 with Docker does not allow mirroring.

 ### Cluster API

@@ -309,7 +309,7 @@ Now that Rancher is deployed, see [Adding TLS Secrets](../getting-started/instal
 The Rancher chart configuration has many options for customizing the installation to suit your specific environment. Here are some common advanced scenarios.

 - [HTTP Proxy](../getting-started/installation-and-upgrade/installation-references/helm-chart-options.md#http-proxy)
- [Private container image Registry](../getting-started/installation-and-upgrade/installation-references/helm-chart-options.md#private-registry-and-air-gap-installs)
+- [Private Container Image Registry](../getting-started/installation-and-upgrade/installation-references/helm-chart-options.md#private-registry-and-air-gap-installs)
 - [TLS Termination on an External Load Balancer](../getting-started/installation-and-upgrade/installation-references/helm-chart-options.md#external-tls-termination)

 See the [Chart Options](../getting-started/installation-and-upgrade/installation-references/helm-chart-options.md) for the full list of options.
@@ -46,4 +46,4 @@ If you need to pass an **IAM Instance Profile Name** (not ARN), for example, whe

 ### Engine Options

-In the **Engine Options** section of the node template, you can configure the container daemon. You may want to specify the container version or a container registry mirror.
+In the **Engine Options** section of the node template, you can configure the container daemon. You may want to specify the container version or a container image registry mirror.
@@ -16,11 +16,9 @@ If using a VNet in a different Resource Group than the VMs, the VNet name should

 :::

-// If you use Docker, the [Docker daemon](https://docs.docker.com/engine/docker-overview/#the-docker-daemon) configuration options include:
+If you use Docker, the [Docker daemon](https://docs.docker.com/engine/docker-overview/#the-docker-daemon) configuration options include:

-// - **Labels:** For information on labels, refer to the [Docker object label documentation.](https://docs.docker.com/config/labels-custom-metadata/)
-// - **Docker Engine Install URL:** Determines what Docker version will be installed on the instance.
-// - **Registry mirrors:** Docker Registry mirror to be used by the Docker daemon
-// - **Other advanced options:** Refer to the [Docker daemon option reference](https://docs.docker.com/engine/reference/commandline/dockerd/)
-
-// Do we update this section or keep it as-is re: references to Docker vs being more generic?
+- **Labels:** For information on labels, refer to the [Docker object label documentation.](https://docs.docker.com/config/labels-custom-metadata/).
+- **Docker Engine Install URL:** Determines what Docker version will be installed on the instance.
+- **Registry mirrors:** Docker Registry mirror to be used by the Docker daemon.
+- **Other advanced options:** Refer to the [Docker daemon option reference](https://docs.docker.com/engine/reference/commandline/dockerd/).
@@ -8,13 +8,11 @@ Account access information is stored as a cloud credential. Cloud credentials ar

 The **Droplet Options** provision your cluster's geographical region and specifications.

-// ### Docker Daemon
+### Docker Daemon

-// If you use Docker, the [Docker daemon](https://docs.docker.com/engine/docker-overview/#the-docker-daemon) configuration options include:
+If you use Docker, the [Docker daemon](https://docs.docker.com/engine/docker-overview/#the-docker-daemon) configuration options include:

-// - **Labels:** For information on labels, refer to the [Docker object label documentation.](https://docs.docker.com/config/labels-custom-metadata/)
-// - **Docker Engine Install URL:** Determines what Docker version will be installed on the instance.
-// - **Registry mirrors:** Docker Registry mirror to be used by the Docker daemon
-// - **Other advanced options:** Refer to the [Docker daemon option reference](https://docs.docker.com/engine/reference/commandline/dockerd/)
-
-// Do we update this section or keep it as-is re: references to Docker vs being more generic?
+- **Labels:** For information on labels, refer to the [Docker object label documentation.](https://docs.docker.com/config/labels-custom-metadata/)
+- **Docker Engine Install URL:** Determines what Docker version will be installed on the instance.
+- **Registry mirrors:** Docker Registry mirror to be used by the Docker daemon
+- **Other advanced options:** Refer to the [Docker daemon option reference](https://docs.docker.com/engine/reference/commandline/dockerd/)