Skip to content

Commit 2d14bd8

Browse files
authored
Merge pull request #87629 from sr1kar99/2136-deprecation-of-siteconfig-v1
TELCODOCS#2136: Deprecation of SiteConfig v1
2 parents b005ecb + 869f6d5 commit 2d14bd8

6 files changed

+17
-0
lines changed

edge_computing/ztp-advanced-install-ztp.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,8 @@ toc::[]
88

99
You can use `SiteConfig` custom resources (CRs) to deploy custom functionality and configurations in your managed clusters at installation time.
1010

11+
include::snippets/siteconfig-deprecation-notice.adoc[]
12+
1113
include::modules/ztp-customizing-the-install-extra-manifests.adoc[leveloffset=+1]
1214

1315
include::modules/ztp-filtering-ai-crs-using-siteconfig.adoc[leveloffset=+1]

modules/ztp-creating-ztp-crs-for-multiple-managed-clusters.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -15,3 +15,5 @@ You can provision single clusters manually or in batches with {ztp}:
1515
Provisioning a single cluster:: Create a single `SiteConfig` CR and related installation and configuration CRs for the cluster, and apply them in the hub cluster to begin cluster provisioning. This is a good way to test your CRs before deploying on a larger scale.
1616

1717
Provisioning many clusters:: Install managed clusters in batches of up to 400 by defining `SiteConfig` and related CRs in a Git repository. ArgoCD uses the `SiteConfig` CRs to deploy the sites. The {rh-rhacm} policy generator creates the manifests and applies them to the hub cluster. This starts the cluster provisioning process.
18+
19+
include::snippets/siteconfig-deprecation-notice.adoc[]

modules/ztp-deploying-a-site.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,8 @@
88

99
Use the following procedure to create a `SiteConfig` custom resource (CR) and related files and initiate the {ztp-first} cluster deployment.
1010

11+
include::snippets/siteconfig-deprecation-notice.adoc[]
12+
1113
.Prerequisites
1214

1315
* You have installed the OpenShift CLI (`oc`).

modules/ztp-generating-install-and-config-crs-manually.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -8,6 +8,8 @@
88

99
Use the `generator` entrypoint for the `ztp-site-generate` container to generate the site installation and configuration custom resource (CRs) for a cluster based on `SiteConfig` and `{policy-gen-cr}` CRs.
1010

11+
include::snippets/siteconfig-deprecation-notice.adoc[]
12+
1113
.Prerequisites
1214

1315
* You have installed the OpenShift CLI (`oc`).

modules/ztp-precaching-ztp-config.adoc

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -13,6 +13,8 @@ In the {ztp-first} provisioning workflow, the {factory-prestaging-tool} requires
1313
* `nodes.installerArgs`
1414
* `nodes.ignitionConfigOverride`
1515
16+
include::snippets/siteconfig-deprecation-notice.adoc[]
17+
1618
.Example SiteConfig with additional fields
1719
[source,yaml]
1820
----
Lines changed: 7 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,7 @@
1+
:_mod-docs-content-type: SNIPPET
2+
[IMPORTANT]
3+
====
4+
SiteConfig v1 is deprecated starting with {product-title} version 4.18. Equivalent and improved functionality is now available through the SiteConfig Operator using the `ClusterInstance` custom resource. For more information, see link:https://access.redhat.com/articles/7105238[Procedure to transition from SiteConfig CRs to the ClusterInstance API].
5+
6+
For more information about the SiteConfig Operator, see link:https://docs.redhat.com/en/documentation/red_hat_advanced_cluster_management_for_kubernetes/2.12/html-single/multicluster_engine_operator_with_red_hat_advanced_cluster_management/index#siteconfig-intro[SiteConfig].
7+
====

0 commit comments

Comments
 (0)