// Module included in the following assemblies:
//
// * scalability_and_performance/ztp_far_edge/ztp-configuring-managed-clusters-policies.adoc

:_mod-docs-content-type: CONCEPT
[id="ztp-policygentemplates-for-ran_{context}"]
= {policy-gen-cr} CRs for RAN deployments

Use `{policy-gen-cr}` custom resources (CRs) to customize the configuration applied to the cluster by using the {ztp-first} pipeline. The `{policy-gen-cr}` CR allows you to generate one or more policies to manage the set of configuration CRs on your fleet of clusters. The `{policy-gen-cr}` CR identifies the set of managed CRs, bundles them into policies, builds the policy wrapping around those CRs, and associates the policies with clusters by using label binding rules.

The reference configuration, obtained from the {ztp} container, is designed to provide a set of critical features and node tuning settings that ensure the cluster can support the stringent performance and resource utilization constraints typical of RAN (Radio Access Network) Distributed Unit (DU) applications. Changes or omissions from the baseline configuration can affect feature availability, performance, and resource utilization. Use the reference `{policy-gen-cr}` CRs as the basis to create a hierarchy of configuration files tailored to your specific site requirements.

The baseline `{policy-gen-cr}` CRs that are defined for RAN DU cluster configuration can be extracted from the {ztp} `ztp-site-generate` container. See "Preparing the {ztp} site configuration repository" for further details.

The `{policy-gen-cr}` CRs can be found in the `./{argocd-folder}` folder. The reference architecture has common, group, and site-specific configuration CRs. Each `{policy-gen-cr}` CR refers to other CRs that can be found in the `./out/source-crs` folder.

The `{policy-gen-cr}` CRs relevant to RAN cluster configuration are described below. Variants are provided for the group `{policy-gen-cr}` CRs to account for differences in single-node, three-node compact, and standard cluster configurations. Similarly, site-specific configuration variants are provided for single-node clusters and multi-node (compact or standard) clusters. Use the group and site-specific configuration variants that are relevant for your deployment.

.{policy-gen-cr} CRs for RAN deployments
[cols=2*, options="header"]
|====
|{policy-gen-cr} CR
|Description

|`{policy-prefix}example-multinode-site.yaml`
|Contains a set of CRs that get applied to multi-node clusters. These CRs configure SR-IOV features typical for RAN installations.

|`{policy-prefix}example-sno-site.yaml`
|Contains a set of CRs that get applied to {sno} clusters. These CRs configure SR-IOV features typical for RAN installations.

|`{policy-prefix}common-mno-ranGen.yaml`
|Contains a set of common RAN policy configuration that get applied to multi-node clusters.

|`{policy-prefix}common-ranGen.yaml`
|Contains a set of common RAN CRs that get applied to all clusters. These CRs subscribe to a set of operators providing cluster features typical for RAN as well as baseline cluster tuning.

|`{policy-prefix}group-du-3node-ranGen.yaml`
|Contains the RAN policies for three-node clusters only.

|`{policy-prefix}group-du-sno-ranGen.yaml`
|Contains the RAN policies for single-node clusters only.

|`{policy-prefix}group-du-standard-ranGen.yaml`
|Contains the RAN policies for standard three control-plane clusters.

|`{policy-prefix}group-du-3node-validator-ranGen.yaml`
|`{policy-gen-cr}` CR used to generate the various policies required for three-node clusters.

|`{policy-prefix}group-du-standard-validator-ranGen.yaml`
|`{policy-gen-cr}` CR used to generate the various policies required for standard clusters.

|`{policy-prefix}group-du-sno-validator-ranGen.yaml`
|`{policy-gen-cr}` CR used to generate the various policies required for {sno} clusters.
|====
