Workloads (feature toggles)

Workload enablement is modeled as data, per environment, in:

• 03-deployment-repository/01-ameide-gitops/layers/cluster/00-platform-baseline-substrate/keptn/resources/workloads.json

How it works

• Each environment has a mergeKey (e.g. local, dev, staging, prod).
• Argo CD ApplicationSet env-scoped layers typically merge:
• the target’s env matrix (config/clusters/<target>.yaml)
• the workload toggles (workloads.json) using the shared mergeKey.

This is what makes workload enablement consistent across targets (AKS/EKS/GKE/K3D) without provider-specific hardcoding.

Practical use

• If an environment is disabled in clusters/<target>.yaml, nothing env-scoped is generated for it (even if workloads are enabled).
• If an environment is enabled, workloads decide what apps/routes/hosts exist in that environment.