Skip to content

Commit 6db3f10

Browse files
authored
Merge pull request #70737 from aireilly/TELCODOCS-1685
TELCODOCS-1685 - Reuse the ArgoCD patch steps for ZTP install and upgrade procedures
2 parents 1bda51f + d84e818 commit 6db3f10

File tree

4 files changed

+31
-41
lines changed

4 files changed

+31
-41
lines changed

_topic_maps/_topic_map.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -2956,6 +2956,8 @@ Topics:
29562956
File: ztp-deploying-far-edge-clusters-at-scale
29572957
- Name: Preparing the hub cluster for ZTP
29582958
File: ztp-preparing-the-hub-cluster
2959+
- Name: Updating GitOps ZTP
2960+
File: ztp-updating-gitops
29592961
- Name: Installing managed clusters with RHACM and SiteConfig resources
29602962
File: ztp-deploying-far-edge-sites
29612963
- Name: Configuring managed clusters with policies and PolicyGenTemplate resources
@@ -2975,8 +2977,6 @@ Topics:
29752977
Distros: openshift-origin,openshift-enterprise
29762978
- Name: Updating managed clusters in a disconnected environment with the Topology Aware Lifecycle Manager
29772979
File: ztp-talm-updating-managed-policies
2978-
- Name: Updating GitOps ZTP
2979-
File: ztp-updating-gitops
29802980
- Name: Expanding single-node OpenShift clusters with GitOps ZTP
29812981
File: ztp-sno-additional-worker-node
29822982
- Name: Pre-caching images for single-node OpenShift deployments

modules/ztp-installing-the-new-gitops-ztp-applications.adoc

Lines changed: 1 addition & 15 deletions
Original file line numberDiff line numberDiff line change
@@ -10,18 +10,4 @@ Using the extracted `argocd/deployment` directory, and after ensuring that the a
1010

1111
.Procedure
1212

13-
. To patch the ArgoCD instance in the hub cluster by using the patch file that you previously extracted into the `update/argocd/deployment/` directory, enter the following command:
14-
+
15-
[source,terminal]
16-
----
17-
$ oc patch argocd openshift-gitops \
18-
-n openshift-gitops --type=merge \
19-
--patch-file update/argocd/deployment/argocd-openshift-gitops-patch.json
20-
----
21-
22-
. To apply the contents of the `argocd/deployment` directory, enter the following command:
23-
+
24-
[source,terminal]
25-
----
26-
$ oc apply -k update/argocd/deployment
27-
----
13+
include::snippets/ztp-patch-argocd-hub-cluster.adoc[]

modules/ztp-preparing-the-hub-cluster-for-ztp.adoc

Lines changed: 2 additions & 24 deletions
Original file line numberDiff line numberDiff line change
@@ -39,27 +39,5 @@ You can configure the hub cluster with a set of ArgoCD applications that generat
3939

4040
*** `path` specifies the path to the `SiteConfig` and `PolicyGenTemplate` CRs, respectively.
4141
42-
. To install the {ztp} plugin you must patch the ArgoCD instance in the hub cluster by using the patch file previously extracted into the `out/argocd/deployment/` directory. Run the following command:
43-
+
44-
[source,terminal]
45-
----
46-
$ oc patch argocd openshift-gitops \
47-
-n openshift-gitops --type=merge \
48-
--patch-file out/argocd/deployment/argocd-openshift-gitops-patch.json
49-
----
50-
51-
. In {rh-rhacm} 2.7 and later, the multicluster engine enables the `cluster-proxy-addon` feature by default.
52-
To disable this feature, apply the following patch to disable and remove the relevant hub cluster and managed cluster pods that are responsible for this add-on.
53-
Run the following command:
54-
+
55-
[source,terminal]
56-
----
57-
$ oc patch multiclusterengines.multicluster.openshift.io multiclusterengine --type=merge --patch-file out/argocd/deployment/disable-cluster-proxy-addon.json
58-
----
59-
60-
. Apply the pipeline configuration to your hub cluster by using the following command:
61-
+
62-
[source,terminal]
63-
----
64-
$ oc apply -k out/argocd/deployment
65-
----
42+
[start=2]
43+
include::snippets/ztp-patch-argocd-hub-cluster.adoc[]
Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
:_mod-docs-content-type: SNIPPET
2+
. To install the {ztp} plugin, patch the ArgoCD instance in the hub cluster by using the patch file that you previously extracted into the `out/argocd/deployment/` directory.
3+
Run the following command:
4+
+
5+
[source,terminal]
6+
----
7+
$ oc patch argocd openshift-gitops \
8+
-n openshift-gitops --type=merge \
9+
--patch-file out/argocd/deployment/argocd-openshift-gitops-patch.json
10+
----
11+
12+
. In {rh-rhacm} 2.7 and later, the multicluster engine enables the `cluster-proxy-addon` feature by default.
13+
Apply the following patch to disable the `cluster-proxy-addon` feature and remove the relevant hub cluster and managed pods that are responsible for this add-on.
14+
Run the following command:
15+
+
16+
[source,terminal]
17+
----
18+
$ oc patch multiclusterengines.multicluster.openshift.io multiclusterengine --type=merge --patch-file out/argocd/deployment/disable-cluster-proxy-addon.json
19+
----
20+
21+
. Apply the pipeline configuration to your hub cluster by running the following command:
22+
+
23+
[source,terminal]
24+
----
25+
$ oc apply -k out/argocd/deployment
26+
----

0 commit comments

Comments
 (0)