From a8e6af6dd0d77acdaa95bb918447b20a78fec7a7 Mon Sep 17 00:00:00 2001 From: Christopher Negus Date: Fri, 29 Sep 2023 20:29:14 +0000 Subject: [PATCH] Changed caption for second image --- docs/content/en/docs/getting-started/airgapped/_index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/docs/content/en/docs/getting-started/airgapped/_index.md b/docs/content/en/docs/getting-started/airgapped/_index.md index 4ffb033440a6..e2de6d3a5926 100644 --- a/docs/content/en/docs/getting-started/airgapped/_index.md +++ b/docs/content/en/docs/getting-started/airgapped/_index.md @@ -12,7 +12,7 @@ The following diagrams illustrate how to set up for cluster creation in an airga If you are planning to run EKS Anywhere in an airgapped environments, before you create a cluster, you must temporarily connect your Admin machine to the internet to install the `eksctl` CLI and pull the required EKS Anywhere dependencies. -![Download EKS Anywhere artifacts to Admin machine](/images/airgap-arch02.png) +![Disconnect Admin machine from Internet to create cluster](/images/airgap-arch02.png) Once these dependencies are downloaded and imported in a local registry, you no longer need internet access. In the EKS Anywhere cluster specification, you can configure EKS Anywhere to use your local registry mirror. When the registry mirror configuration is set in the EKS Anywhere cluster specification, EKS Anywhere configures containerd to pull from that registry instead of Amazon ECR during cluster creation and lifecycle operations. For more information, reference the [Registry Mirror Configuration documentation.]({{< relref "../optional/registrymirror" >}})