sure, messaged you there

What does the command kubectl get ks <name> -n <namespace> -o jsonpath='{.spec.wait}' show?

@matheuscscp it returns nothing.

To sum up we spend some time to figure out what might be the issue and to see any drop we used patch with concurrent-ssa.
Due to very heavy workloads (over 6000 entries into inventory) we only managed to drop around 30 seconds/1 minute from reconcile time. It also might be an indication that AKS controlplane can be slower than GKE (@stefanprodan tested it on GKE and the time dropped from 4 mins to 2 mins with --concurrent-ssa=10 - not confirmed as we didn't have mirroring workloads/cluster setup)

In the end the solution to my problem might be to split the main kustomization into several smaller ones to make the time be much more acceptable, but I will be doing more testing.

  - patch: |
      - op: add
        path: /spec/template/spec/containers/0/args/-
        value: --concurrent=20
      - op: add
        path: /spec/template/spec/containers/0/args/-
        value: --concurrent-ssa=20
      - op: replace
        path: /spec/template/spec/volumes/0
        value:
          name: temp
          emptyDir:
            medium: Memory
    target:
      kind: Deployment
      name: kustomize-controller
  - patch: |
      apiVersion: apps/v1
      kind: Deployment
      metadata:
        name: all
      spec:
        template:
          spec:
            containers:
              - name: manager
                resources:
                  limits:
                    cpu: 4000m
                    memory: 4Gi

over 6000 entries into inventory

Maybe it would make sense to break this Kustomization down a little bit into a few more Kustomizations?

Probably that will be the approach I will be recommending and implementing for this tenant. Thank you for your help