Skip to content

docs: add air-gapped environment guidance for private registry #6558

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
Shivampal157 wants to merge 1 commit into
base: main
Choose a base branch
from
Open

docs: add air-gapped environment guidance for private registry #6558

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
17 changes: 16 additions & 1 deletion docs/versioned/serving/deploying-from-private-registry.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -89,4 +89,19 @@ You can configure your Knative cluster to deploy images from a private registry
env:
- name: TARGET
value: "World"
```
```
## Air-gapped environments

In air-gapped environments, the Kubernetes cluster does not have outbound
internet access. Before deploying Knative Serving workloads, ensure that all
required container images are available in an internal or private registry.

When operating in an air-gapped setup:

- Mirror all required Knative Serving and application images to a private registry.
- Ensure Kubernetes nodes can authenticate to and pull images from the private registry.
- Make sure installation manifests and YAML files are available locally.

After completing these steps, follow the same procedure described above to
configure imagePullSecrets so that Knative Services and Revisions can pull
images from the private registry.
Loading