From 949f994d10e9a40986ee605f4d4aeda69a0fe465 Mon Sep 17 00:00:00 2001 From: martyav Date: Thu, 5 Jan 2023 13:24:42 -0500 Subject: [PATCH] second pass, marking content that needs technical help --- .../infrastructure-private-registry.md | 12 ++++++-- .../kubernetes-and-docker-registries.md | 28 +++++++++++-------- .../node-template-configuration/azure.md | 12 ++++---- .../digitalocean.md | 14 ++++++---- 4 files changed, 41 insertions(+), 25 deletions(-) diff --git a/docs/getting-started/installation-and-upgrade/other-installation-methods/air-gapped-helm-cli-install/infrastructure-private-registry.md b/docs/getting-started/installation-and-upgrade/other-installation-methods/air-gapped-helm-cli-install/infrastructure-private-registry.md index 8ac9bc41499..a18a7cf9987 100644 --- a/docs/getting-started/installation-and-upgrade/other-installation-methods/air-gapped-helm-cli-install/infrastructure-private-registry.md +++ b/docs/getting-started/installation-and-upgrade/other-installation-methods/air-gapped-helm-cli-install/infrastructure-private-registry.md @@ -84,7 +84,9 @@ Rancher supports air gap installs using a private registry. You must have your o In a later step, when you set up your K3s Kubernetes cluster, you will create a [private registries configuration file](https://rancher.com/docs/k3s/latest/en/installation/private-registry/) with details from this registry. -If you need help with creating a private registry, please refer to the [official Docker documentation.](https://docs.docker.com/registry/deploying/#run-an-externally-accessible-registry) +// If you need help with creating a private registry, please refer to the [official Docker documentation.](https://docs.docker.com/registry/deploying/#run-an-externally-accessible-registry) + +// Need to update link @@ -151,7 +153,9 @@ Rancher supports air gap installs using a secure private registry. You must have In a later step, when you set up your RKE Kubernetes cluster, you will create a [private registries configuration file](https://rancher.com/docs/rke/latest/en/config-options/private-registries/) with details from this registry. -If you need help with creating a private registry, please refer to the [official Docker documentation.](https://docs.docker.com/registry/deploying/#run-an-externally-accessible-registry) +// If you need help with creating a private registry, please refer to the [official Docker documentation.](https://docs.docker.com/registry/deploying/#run-an-externally-accessible-registry) + +// Need to update link @@ -176,7 +180,9 @@ For an example of one way to set up Linux nodes, refer to this [tutorial](../../ Rancher supports air gap installs using a private registry on your bastion server. You must have your own private registry or other means of distributing container images to your machines. -If you need help with creating a private registry, please refer to the [official Docker documentation.](https://docs.docker.com/registry/) +// If you need help with creating a private registry, please refer to the [official Docker documentation.](https://docs.docker.com/registry/) + +// Need to update link diff --git a/docs/how-to-guides/new-user-guides/kubernetes-resources-setup/kubernetes-and-docker-registries.md b/docs/how-to-guides/new-user-guides/kubernetes-resources-setup/kubernetes-and-docker-registries.md index 7a35414055d..17acc06276e 100644 --- a/docs/how-to-guides/new-user-guides/kubernetes-resources-setup/kubernetes-and-docker-registries.md +++ b/docs/how-to-guides/new-user-guides/kubernetes-resources-setup/kubernetes-and-docker-registries.md @@ -17,7 +17,8 @@ Currently, deployments pull the private registry credentials automatically only :::note Prerequisite: -You must have a [private registry](https://docs.docker.com/registry/deploying/) available to use. +// You must have a [private registry](https://docs.docker.com/registry/deploying/) available to use. +// Need appropriate replacement link ::: @@ -48,7 +49,8 @@ You must have a [private registry](https://docs.docker.com/registry/deploying/) :::note Prerequisites: -You must have a [private registry](https://docs.docker.com/registry/deploying/) available to use. +// You must have a [private registry](https://docs.docker.com/registry/deploying/) available to use. +// Need appropriate replacement link ::: @@ -131,18 +133,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= \ - --docker-password= -``` +// ``` +// kubectl create secret docker-registry testquay \ +// --docker-server=quay.io \ +// --docker-username= \ +// --docker-password= +// ``` + +// 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 The result looks like this: diff --git a/docs/reference-guides/cluster-configuration/downstream-cluster-configuration/node-template-configuration/azure.md b/docs/reference-guides/cluster-configuration/downstream-cluster-configuration/node-template-configuration/azure.md index b5283c9a4ac..d832fd4a36f 100644 --- a/docs/reference-guides/cluster-configuration/downstream-cluster-configuration/node-template-configuration/azure.md +++ b/docs/reference-guides/cluster-configuration/downstream-cluster-configuration/node-template-configuration/azure.md @@ -16,9 +16,11 @@ 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/) \ No newline at end of file +// - **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? \ No newline at end of file diff --git a/docs/reference-guides/cluster-configuration/downstream-cluster-configuration/node-template-configuration/digitalocean.md b/docs/reference-guides/cluster-configuration/downstream-cluster-configuration/node-template-configuration/digitalocean.md index 273df0efd80..df84e209217 100644 --- a/docs/reference-guides/cluster-configuration/downstream-cluster-configuration/node-template-configuration/digitalocean.md +++ b/docs/reference-guides/cluster-configuration/downstream-cluster-configuration/node-template-configuration/digitalocean.md @@ -8,11 +8,13 @@ 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/) \ No newline at end of file +// - **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? \ No newline at end of file