mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
78 lines
2.8 KiB
Plaintext
78 lines
2.8 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * edge_computing/ztp-migrate-clusterinstance.adoc
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="ztp-active-ocp-version_{context}"]
|
|
= Transitioning the active-ocp-version ClusterImageSet
|
|
|
|
Optionally, the `active-ocp-version` `ClusterImageSet` is a {ztp-first} convention used in {ztp} deployments.
|
|
It provides a single, central definition of the {product-title} release image to use when provisioning clusters.
|
|
By default, this resource is synchronized to the hub cluster from the `site-config/resources/` folder.
|
|
|
|
If your deployment uses an `active-ocp-version` `ClusterImageSet` CR, you must migrate it to the `resources/` folder in the new directroy that contains `ClusterInstance` CRs.
|
|
This prevents synchronization conflicts because both Argo CD applications cannot manage the same resource.
|
|
|
|
.Prerequisites
|
|
|
|
* You have completed the procedure to create the parallel Argo CD pipeline for `ClusterInstance` CRs.
|
|
* The Argo CD application points to the folder in your Git repository that will contain the new `ClusterInstance` CRs and associated cluster resouces. In this example, the `site-configs-v2/` Argo CD application points to the `site-configs-v2/` folder.
|
|
* Your Git repository contains an `active-ocp-version.yaml` manifest in the `resources/` folder.
|
|
|
|
.Procedure
|
|
|
|
. Copy the `resources/` folder from the `site-configs/` directory into the new `site-configs-v2/` directory:
|
|
+
|
|
[source,bash]
|
|
----
|
|
$ cp -r site-configs/resources site-configs-v2/
|
|
----
|
|
|
|
. Remove the reference to the `resources/` folder from the `site-configs/kustomization.yaml` file.
|
|
This ensures that the old `clusters` Argo CD application no longer manages the `active-ocp-version` resource.
|
|
+
|
|
.Example updated `site-configs/resources/kustomization.yaml` file
|
|
[source,yaml]
|
|
----
|
|
apiVersion: kustomize.config.k8s.io/v1beta1
|
|
kind: Kustomization
|
|
resources:
|
|
- pre-reqs/
|
|
#- resources/
|
|
generators:
|
|
- hub-1/sno1.yaml
|
|
- hub-1/sno2.yaml
|
|
- hub-1/sno3.yaml
|
|
----
|
|
|
|
. Add the `resources/` folder to the `site-configs-v2/kustomization.yaml` file.
|
|
This step transfers ownership of the `ClusterImageSet` to the new `clusters-v2` application.
|
|
+
|
|
.Example updated `site-configs-v2/kustomization.yaml` file
|
|
[source,yaml]
|
|
----
|
|
apiVersion: kustomize.config.k8s.io/v1beta1
|
|
kind: Kustomization
|
|
resources:
|
|
- resources/
|
|
----
|
|
|
|
. Commit and push the changes to the Git repository.
|
|
|
|
.Verification
|
|
|
|
. In Argo CD, verify that the `clusters-v2` application is *Healthy* and *Synced*.
|
|
|
|
. If the `active-ocp-version` `ClusterImageSet` resource in the `cluster` Argo application is out of sync, you can remove the Argo CD application label by running the following command:
|
|
+
|
|
[source,bash]
|
|
----
|
|
$ oc label clusterimageset active-ocp-version app.kubernetes.io/instance-
|
|
----
|
|
+
|
|
.Example output
|
|
[source,bash]
|
|
----
|
|
clusterimageset.hive.openshift.io/active-ocp-version unlabeled
|
|
----
|