## [Declarative configuration for Cluster Overrides](https://docs.rafay.co/blog/2023/11/28/declarative-configuration-for-cluster-overrides/)

### [Cluster overrides](https://docs.rafay.co/blog/2023/11/28/declarative-configuration-for-cluster-overrides/#cluster-overrides)

By default, K8s objects require certain values be set inside their specs that match the cluster's configuration. If this were to done within the add-on (or workload) manifest, it would require that many duplicate add-ons (or workloads) would need to be created for a fleet of clusters. To mitigate this, the platform supports cluster overrides. These allow the customer to use a single add-on (or workload) org wide and dynamically inject values into a manifest as it is being deployed to the cluster.

Examples include:

- Use of a different license key for a security tool based on the business unit

- Configuration of different resource requests for a monitoring tool based on environment type (test or prod)

- Dynamic configuration of cluster name during deployment of a load balancer (e.g. AWS Load Balancer)