Skip to content
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

TELCODOCS-1828: Clarify supported format for osImages.openshiftVersion in ZTP docs #86715

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

TELCODOCS-1828: Clarify supported format for osImages.openshiftVersion in ZTP docs #86715

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
12 changes: 7 additions & 5 deletions modules/ztp-configuring-the-cluster-for-a-disconnected-environment.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -54,6 +54,7 @@ data:
<3> The configuration file for the mirror registry. The mirror registry configuration adds mirror information to the `/etc/containers/registries.conf` file in the discovery image. The mirror information is stored in the `imageContentSources` section of the `install-config.yaml` file when the information is passed to the installation program. The Assisted Service pod that runs on the hub cluster fetches the container images from the configured mirror registry.
<4> The URL of the mirror registry. You must use the URL from the `imageContentSources` section by running the `oc adm release mirror` command when you configure the mirror registry. For more information, see the _Mirroring the OpenShift Container Platform image repository_ section.
<5> The registries defined in the `registries.conf` file must be scoped by repository, not by registry. In this example, both the `quay.io/example-repository` and the `mirror1.registry.corp.com:5000/example-repository` repositories are scoped by the `example-repository` repository.

+
This updates `mirrorRegistryRef` in the `AgentServiceConfig` custom resource, as shown below:
+
Expand Down Expand Up @@ -84,12 +85,13 @@ spec:
mirrorRegistryRef:
name: assisted-installer-mirror-config <2>
osImages:
- openshiftVersion: <ocp_version>
url: <iso_url> <3>
- openshiftVersion: <ocp_version> <3>
url: <iso_url> <4>
----
<1> Set the `AgentServiceConfig` namespace to `multicluster-engine` to match the `ConfigMap` namespace
<2> Set `mirrorRegistryRef.name` to match the definition specified in the related `ConfigMap` CR
<3> Set the URL for the ISO hosted on the `httpd` server
<1> Set the `AgentServiceConfig` namespace to `multicluster-engine` to match the `ConfigMap` namespace.
<2> Set `mirrorRegistryRef.name` to match the definition specified in the related `ConfigMap` CR.
<3> Set the {product-title} version to either the x.y or x.y.z format.
<4> Set the URL for the ISO hosted on the `httpd` server.

[IMPORTANT]
====
Expand Down