Skip to content

Environments

Ameide treats targets and environments as separate axes:

  • Targets are physical clusters (e.g. k3d, aks, eks, gke).
  • Environments are namespaces inside a target cluster and are always named:
  • local, dev, staging, prod

Enablement (single source of truth)

Environment fan-out is controlled by the enabled: "true|false" flag in the per-target env matrix:

  • 03-deployment-repository/01-ameide-gitops/layers/infra/L10-foundations/config/clusters/k3d.yaml
  • 03-deployment-repository/01-ameide-gitops/layers/infra/L10-foundations/config/clusters/aks.yaml
  • 03-deployment-repository/01-ameide-gitops/layers/infra/L10-foundations/config/clusters/eks.yaml
  • 03-deployment-repository/01-ameide-gitops/layers/infra/L10-foundations/config/clusters/gke.yaml

Argo CD ApplicationSet generators read these files and filter out disabled environments, so no Argo Applications are generated for environments where enabled: "false".

Common operations

  • Disable an environment: set its enabled flag to "false" in the relevant target’s clusters/<target>.yaml.
  • Re-enable an environment: set its enabled flag back to "true".

Notes

  • The namespace name (namespace:) is part of the environment matrix and is the destination namespace Argo uses for env-scoped layers.
  • Workload toggles are separate from environment enablement (see Platform → Workloads).