fleet.yaml without helm section no longer creates bundle

[adibrastegarnia]

Is there an existing issue for this?

• [x] I have searched the existing issues

Current Behavior

In earlier versions of fleet (0.10.2), we were able to define a fleet.yaml file without specifying a helm chart and fleet would still create a bundle for that directory. We recently upgraded to use 0.12.2 and same fleet.yaml does not trigger bundle generation. We were using this approach to inject some labels to a namespace resource that is required for another bundle (using depend on). here is an example of fleet.yaml which we are using

name: test-namespaces-94kdg
labels: {}
defaultNamespace: test
deleteCRDResources: false
helm:
  releaseName: ""
  repo: ""
  chart: ""
  version: ""
  valuesFiles: []
dependsOn: []
namespaceLabels:
  name: test

Is this expected behavior?

Expected Behavior

Bundle gets created even the helm section is not specifying a helm chart.

Steps To Reproduce

No response

Environment

- Architecture: kind, RKE
- Fleet Version:0.12.2
- Cluster:
  - Provider:
  - Options:
  - Kubernetes Version:

Logs

Anything else?

No response

[manno]

The bundle did not deploy any resources? It's only function was to label a namespace? That did work, fleet installed an empty helm chart?

We recently excluded fleet.yaml from the bundle, as it is never deployed. That might have made your bundle emptier than before.

As a workaround, you could put an empty configmap next to the fleet.yaml?

[adibrastegarnia]

Thanks for your response @manno. yeah the problem is the bundle is not getting created in the first place and since another bundle depends on it fails to become ready. An error like this:

message: 'list bundledeployments: no bundles matching labels fleet.cattle.io/bundle-name=test-rt8ts,fleet.cattle.io/bundle-namespace=52c6a303-6fc5-4d82-8cd5-62b97fabf51d

Let me try the configmap workaround and get back to you with more details.

[adibrastegarnia]

I tried adding an empty ConfigMap, and the bundle gets created successfully. @manno , could we get a fix for this to prevent the creation of an unnecessary resource?

[adibrastegarnia]

I noticed even an empty yaml file is enough to trigger it.