mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 12:46:18 +01:00
36 lines
1.4 KiB
Plaintext
36 lines
1.4 KiB
Plaintext
// Module included in the following assemblies:
|
|
//
|
|
// * scalability_and_performance/ztp_far_edge/ztp-deploying-far-edge-sites.adoc
|
|
|
|
:_mod-docs-content-type: PROCEDURE
|
|
[id="ztp-site-cleanup_{context}"]
|
|
= Removing a managed cluster site from the {ztp} pipeline
|
|
|
|
You can remove a managed site and the associated installation and configuration policy CRs from the {ztp-first} pipeline.
|
|
|
|
.Prerequisites
|
|
|
|
* You have installed the OpenShift CLI (`oc`).
|
|
|
|
* You have logged in to the hub cluster as a user with `cluster-admin` privileges.
|
|
|
|
.Procedure
|
|
|
|
. Remove a site and the associated CRs by removing the associated `ClusterInstance` and `PolicyGenerator` or `PolicyGentemplate` files from the `kustomization.yaml` file.
|
|
|
|
. Add the following `syncOptions` field to the ArgoCD application that manages the target site.
|
|
+
|
|
[source,yaml]
|
|
----
|
|
kind: Application
|
|
spec:
|
|
syncPolicy:
|
|
syncOptions:
|
|
- PrunePropagationPolicy=background
|
|
----
|
|
+
|
|
When you run the {ztp} pipeline again, the generated CRs are removed.
|
|
|
|
. Optional: If you want to permanently remove a site, you should also remove the `ClusterInstance` and site-specific `PolicyGenerator` or `PolicyGentemplate` files from the Git repository.
|
|
|
|
. Optional: If you want to remove a site temporarily, for example when redeploying a site, you can leave the `ClusterInstance` and site-specific `PolicyGenerator` or `PolicyGentemplate` CRs in the Git repository. |