Nested Kustomizations with dependsOn failing dry-run

[darylgraham]

Hi all,

I'm trying to install the Datadog Agent and Operator. The Operator provides the CRDs that are used in the Agent manifest, so I have a "Core" Kustomization that points to an OCI source. That source image has 2 folders, one for each component, and an overlay.yaml that sits at the root of the image and defines a Kustomization for each component. The Agent Kustomization depends on the Operator.

After applying that to the cluster, the Core Kustomization is failing with the error message: DatadogAgent/datadog/datadog-agent dry-run failed: no matches for kind "DatadogAgent" in version "datadoghq.com/v2alpha1"

The only hint I have that might be causing this is that the Operator installs via a HelmRelease. The datadog-operator chart does not contain the CRDs directly, but has a dependency on a second helm chart. Could this be causing the issue?

Files below:

# core-datadog.yaml
apiVersion: kustomize.toolkit.fluxcd.io/v1
kind: Kustomization
metadata:
  name: core-datadog
  namespace: flux-system
spec:
  path: "./"
  interval: 60m
  prune: true
  wait: false
  sourceRef:
    kind: OCIRepository
    name: core-datadog

# overlay.yaml
---
apiVersion: kustomize.toolkit.fluxcd.io/v1
kind: Kustomization
metadata:
  name: datadog-operator
spec:
  interval: 60m0s
  wait: true
  prune: true
  force: false
  sourceRef:
    kind: OCIRepository
    name: core-datadog
  path: "./datadog-operator"
---
apiVersion: kustomize.toolkit.fluxcd.io/v1
kind: Kustomization
metadata:
  name: datadog-agent
spec:
  dependsOn:
    - name: datadog-operator
  interval: 60m0s 
  wait: true 
  prune: true 
  force: false
  sourceRef:
    kind: OCIRepository
    name: core-datadog
  path: "./datadog-agent"

[rssnyder]

@darylgraham did you ever figure this out? Facing the same thing with metallb which also keeps its CRDs in a subchart.