-
Notifications
You must be signed in to change notification settings - Fork 1.9k
OSDOCS-17918: configuring external registry #107199
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.
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
skopacz1
wants to merge
1
commit into
openshift:main
Choose a base branch
from
skopacz1:OSDOCS-17918
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Changes from all commits
Commits
File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,38 @@ | ||
| :_mod-docs-content-type: ASSEMBLY | ||
| [id="configuring-registry-external"] | ||
| = Configuring your cluster to use an external registry | ||
| include::_attributes/common-attributes.adoc[] | ||
| :context: configuring-registry-external | ||
|
|
||
| toc::[] | ||
|
|
||
| [role="_abstract"] | ||
| If your cluster was installed without an external registry, you can configure the cluster to use an external registry as a postinstallation task in order to use a mirroring workflow for your image management. | ||
|
|
||
| [IMPORTANT] | ||
| ==== | ||
| This configuration is applicable only to clusters installed using the method described in xref:../installing/installing_with_agent_based_installer/installing-ove.adoc#installing-ove[Installing a cluster without an external registry]. | ||
| ==== | ||
|
|
||
| When you install a cluster using the method described in "Installing a cluster without an external registry", the cluster relies on images contained in the downloaded ISO for its lifecycle management. | ||
| However, you might want to configure your cluster to use an external image registry and mirror images to the registry instead. | ||
| To do this, you must set up an external registry, successfully complete an update using images from the external registry, and finally delete `InternalReleaseImage` custom resource, which maintains an internal image registry in the cluster. | ||
|
|
||
| :FeatureName: Configuring your cluster to use an external registry | ||
| include::snippets/technology-preview.adoc[] | ||
|
|
||
| // Pre-configuration tasks | ||
| include::modules/converting-external-registry-prereqs.adoc[leveloffset=+1] | ||
|
|
||
| [role="_additional-resources"] | ||
| .Additional resources | ||
| * xref:../disconnected/installing-mirroring-creating-registry.adoc#installing-mirroring-creating-registry[Creating a mirror registry with mirror registry for Red{nbsp}Hat OpenShift] | ||
| * xref:../disconnected/about-installing-oc-mirror-v2.adoc#about-installing-oc-mirror-v2[Mirroring images for a disconnected installation by using the oc-mirror plugin v2] | ||
| * xref:../disconnected/updating/disconnected-update-osus.adoc#updating-disconnected-cluster-osus[Updating a cluster in a disconnected environment using the OpenShift Update Service] | ||
|
|
||
| // Deleting the internal image registry | ||
| include::modules/converting-external-registry-delete.adoc[leveloffset=+1] | ||
|
|
||
| [role="_additional-resources"] | ||
| .Additional resources | ||
| * xref:../installing/installing_with_agent_based_installer/installing-ove.adoc#installing-ove[Installing a cluster without an external registry] |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,27 @@ | ||
| :_mod-docs-content-type: PROCEDURE | ||
| [id="converting-external-registry-delete_{context}"] | ||
| = Deleting the internal image registry | ||
|
|
||
| [role="_abstract"] | ||
| You can complete configuring your cluster to use an external image registry by deleting the resource responsible for maintaining the internal image registry that was installed on your cluster. | ||
|
|
||
| .Prerequisites | ||
|
|
||
| * You installed your cluster using the method described in "Installing a cluster without an external registry". | ||
| * You have successfully performed a cluster update using images mirrored to your external image registry. | ||
| You can ensure that your cluster has been updated to this new version by running the `oc get clusterversion` command. | ||
| + | ||
| [IMPORTANT] | ||
| ==== | ||
| The version you updated your cluster to must not be listed in the `status.releases` field of the `InternalReleaseImage` custom resource (CR). | ||
| You can check the contents of the CR by running the `oc get InternalReleaseImage -o yaml` command. | ||
| ==== | ||
|
|
||
| .Procedure | ||
|
|
||
| * Delete the singleton `InternalReleaseImage` CR by running the following command: | ||
| + | ||
| [source,terminal] | ||
| ---- | ||
| $ oc delete internalreleaseimages cluster | ||
| ---- | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,17 @@ | ||
| :_mod-docs-content-type: CONCEPT | ||
| [id="converting-external-registry-prereqs_{context}"] | ||
| = Pre-configuration tasks | ||
|
|
||
| [role="_abstract"] | ||
| Before you can configure your cluster to use an external registry, you must prepare your environment with an image registry and perform an update using images on the registry. | ||
|
|
||
| To prevent the accidental deletion of the cluster's internal image registry, you cannot delete the `InternalReleaseImage` custom resource without first having completed the following tasks: | ||
|
|
||
| * You have created a mirror registry in your environment. | ||
| For more information, see "Creating a mirror registry with mirror registry for Red{nbsp}Hat OpenShift". | ||
|
|
||
| * You have mirrored images to the mirror registry. | ||
| For more information, see "Mirroring images for a disconnected installation by using the oc-mirror plugin v2". | ||
|
|
||
| * You have updated your cluster using the images you mirrored to your registry. | ||
| For more information, see "Updating a cluster in a disconnected environment using the OpenShift Update Service". |
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It may be worth noting, as an additional check, to ensure that the current clusterversion version resource is pointing to the new upgraded version. Not sure if it's too obvious, given the previous phrase
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What would the command for that be?
oc get clusterversion? I can add a statement here about using that command to double checkThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yes. And the returned installed version must not be listed in the IRI status releases list.