Looking for modular, independent cluster sub-folder structure

[pred2k]

I'm currently building a simple, modular, and independent folder structure under cluster/my-cluster-dev/.

My goal is to pull the folders (e.g. metrics-server, external-secrets, external-dns,..) under cluster/my-cluster-dev/ from an external template Git repository after flux bootstrap ....

All components under cluster/my-cluster-dev/ or cluster/my-cluster-prod/ should be configured so that changes can be made to my-cluster-dev without affecting my-cluster-prod in any kind!

The structure is roughly as follows:

├── clusters
│   ├── my-cluster-dev
│       ├── external-dns
│       │   ├── external-dns.yaml
│       │   └── helm
│       │       └── external-dns.yaml
│       ├── external-secrets
│       │   ├── cluster-secret-store
│       │   │   └── cluster-secret-store.yaml
│       │   ├── external-secrets.yaml
│       │   └── helm
│       │       └── external-secrets.yaml
│       ├── flux-system
│       │   ├── gotk-components.yaml
│       │   ├── gotk-sync.yaml
│       │   └── kustomization.yaml
│       ├── metrics-server
│       │   └── metrics-server.yaml

clusters/my-cluster-dev/external-secrets/cluster-secret-store/cluster-secret-store.yaml:

---
apiVersion: external-secrets.io/v1
kind: ClusterSecretStore
metadata:
  name: cluster-aws-secretmanager
spec:
  provider:
    aws:
      service: SecretsManager
      region: eu-central-1

clusters/my-cluster-dev/external-secrets/helm/external-secrets.yaml:

---
apiVersion: source.toolkit.fluxcd.io/v1
kind: HelmRepository
metadata:
  name: external-secrets
  namespace: flux-system
spec:
  interval: 10m
  url: https://charts.external-secrets.io
---
apiVersion: helm.toolkit.fluxcd.io/v2
kind: HelmRelease
metadata:
  name: external-secrets
  namespace: flux-system
spec:
  install:
    crds: CreateReplace
    createNamespace: true
    remediation:
      retries: 3
  upgrade:
    crds: CreateReplace
    remediation:
      retries: 3
  releaseName: external-secrets
  targetNamespace: external-secrets
  interval: 10m
  chart:
    spec:
      chart: external-secrets
      version: 0.18.2  # Chart version is the same as application version. See https://github.com/external-secrets/external-secrets/releases
      sourceRef:
        kind: HelmRepository
        name: external-secrets
        namespace: flux-system
  values:
    ....

clusters/my-cluster-dev/external-secrets/external-secrets.yaml:

---
apiVersion: kustomize.toolkit.fluxcd.io/v1
kind: Kustomization
metadata:
  name: external-secrets
  namespace: flux-system
spec:
  interval: 5m
  path: ./clusters/my-cluster-dev/external-secrets/helm
  sourceRef:
    kind: GitRepository
    name: flux-system
  prune: true
  wait: true  # necessary to have the CRDs present, when cluster-secret-store should be installed
---
apiVersion: kustomize.toolkit.fluxcd.io/v1
kind: Kustomization
metadata:
  name: cluster-secret-store
  namespace: flux-system
spec:
  dependsOn:
    - name: external-secrets
  interval: 5m
  path: ./clusters/my-cluster-dev/external-secrets/cluster-secret-store
  sourceRef:
    kind: GitRepository
    name: flux-system
  prune: true

These Kustomization are designed to allow me to easily set spec.dependsOn between the Helm components.

Question: How can I make the spec.path relative and not require it to contain the cluster name, so that the external-secrets/ folder can be copied from a template? Do you other suggestions?

[stefanprodan]

Check out the D2 reference architecture, infra components are versioned and deployed independently: https://github.com/controlplaneio-fluxcd/d2-fleet