Fleet GitOps

In Development (Q4 2026)

This feature is currently in development. Fleet GitOps patterns described here are subject to change.

Purpose: For platform engineers, explains how to distribute GitOps configurations across a fleet of clusters using fleet-level Kustomizations and cluster selectors.

Concept

Fleet GitOps extends the single-cluster FluxCD model to multiple clusters:

Fleet GitOps Repo
├── base/              # Shared across all clusters
├── groups/
│   ├── production/    # All production clusters
│   └── staging/       # All staging clusters
└── clusters/
    ├── prod-us-01/    # Cluster-specific overrides
    └── prod-eu-01/

Fleet Kustomization

A FleetKustomization targets a group of clusters:

apiVersion: fleet.opencenter.cloud/v1alpha1
kind: FleetKustomization
metadata:
  name: security-baseline
spec:
  source:
    path: ./base/security
  target:
    clusterSelector:
      matchLabels:
        environment: production
  interval: 10m

Targeting Strategies

Strategy	Use Case	Example
All clusters	Platform-wide baseline	Security policies, observability
Label selector	Environment-specific	Production-only configs
Cluster group	Regional targeting	EU data residency policies
Named cluster	Cluster-specific override	Custom service configuration

Conflict Resolution

When multiple FleetKustomizations target the same cluster:

• Priority field determines precedence (higher number wins)
• Cluster-specific overrides always win over group-level
• Drift detection alerts when a spoke diverges from fleet intent