Skip to content

cluster kustomizations not used when using az cli? #22

@RoFz

Description

@RoFz

I have just deployed a new AKS and it seems that the contents of the clusters/ directory are not being used by flux when it gets deployed via az cli using the command included in this repo's README:

az k8s-configuration flux create -g flux-demo-rg -c flux-demo-arc -n cluster-config --namespace cluster-config -t connectedClusters --scope cluster -u https://github.com/Azure/gitops-flux2-kustomize-helm-mt --branch main  --kustomization name=infra path=./infrastructure prune=true --kustomization name=apps path=./apps/staging prune=true dependsOn=["infra"]

If I look for kustomizations in the cluster, I can not find any other than those referenced in the az k8s-configuration flux create command:

NAMESPACE        NAME                   AGE   READY   STATUS
cluster-config   cluster-config-apps    43m   True    Applied revision: main@sha1:3dbc5deb98d5a8099d06def8f40628ab103b0330
cluster-config   cluster-config-infra   43m   True    Applied revision: main@sha1:3dbc5deb98d5a8099d06def8f40628ab103b0330

Is that correct (that the clusters/* kustomizations are not used)?

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions