Global configuration reference

Every validated pattern includes a values-global.yaml file at the repository root. This file defines configuration settings that apply across all clusters and environments in the pattern.

`global` section

The global section contains settings that Helm distributes to all sub-charts in the pattern.

`global.pattern`

Specifies the name of the validated pattern. The framework uses this value internally to identify the pattern.

global:
  pattern: multicloud-gitops

Do not change this value unless you are creating a new pattern.

`global.options`

The options block sets default behaviors for operator management and ArgoCD synchronization across all clusters.

global:
  options:
    useCSV: false
    syncPolicy: Automatic
    installPlanApproval: Automatic

Table 1. Options fields
Field	Default	Description
`syncPolicy`	`Automatic`	Sets the default ArgoCD synchronization policy. `Automatic` syncs changes from Git to the cluster without manual intervention. `Manual` requires an administrator to trigger each sync.
`installPlanApproval`	`Automatic`	Controls how Operator Lifecycle Manager (OLM) handles operator upgrades. With `Automatic`, operators check for and apply updates periodically. `Manual` requires an administrator to approve each upgrade.
`useCSV`	`false`	Determines whether subscriptions use specific `ClusterServiceVersions` (CSV) for operator installation. When set to `false`, the subscription channel determines which version to install. Set to `true` when you need to pin operators to specific versions.

`main` section

The main section defines settings for the primary cluster that manages the pattern.

`main.clusterGroupName`

Identifies the main ClusterGroup, which acts as the hub or starting point for the pattern. A ClusterGroup represents a set of clusters that share nearly identical configurations and serve a common architectural purpose.

main:
  clusterGroupName: hub

The value must match a corresponding values-<clusterGroupName>.yaml file in the repository. For example, clusterGroupName: hub requires a values-hub.yaml file. Most patterns use hub for the primary cluster.

For more information about ClusterGroups, see ClusterGroup in values files.

`main.multiSourceConfig`

Controls whether ArgoCD uses multi-source applications, enabling Helm charts to be fetched from external repositories in addition to the local Git repository.

main:
  multiSourceConfig:
    enabled: true

Table 2. multiSourceConfig fields
Field	Default	Description
`enabled`	`true`	Enables multi-source ArgoCD applications. This is the recommended setting for most deployments.
`clusterGroupChartVersion`	(optional)	Constrains the version of the ClusterGroup Helm chart to fetch. Accepts semver ranges such as `0.9.*`.
`helmRepoUrl`	(optional)	Overrides the Helm chart repository URL. Use this for disconnected or air-gapped environments where charts are hosted on an internal registry.

For more information about disconnected environments, see Disconnected installation.

Example `values-global.yaml`

The following example shows a typical values-global.yaml file for the Multicloud GitOps pattern:

---
global:
  pattern: multicloud-gitops

  options:
    useCSV: false
    syncPolicy: Automatic
    installPlanApproval: Automatic

main:
  clusterGroupName: hub

  multiSourceConfig:
    enabled: true

For most patterns, the default values provide a working configuration. Customize specific fields only when your environment requires different behavior, such as pinning operator versions or deploying in a disconnected environment.

Additional resources

Edit this page Open a documentation issue

Global configuration reference

global section

global.pattern

global.options

main section

main.clusterGroupName

main.multiSourceConfig

Example values-global.yaml