Fleet doesn't detect when Helm values from Secrets or ConfigMaps change

[thomashoell]

Is there an existing issue for this?

• [X] I have searched the existing issues

Current Behavior

I have a bundle where I import values from a secret like this:

helm:
  valuesFrom:
    - secretKeyRef:
        name: secret-values
        key: values.yaml

When this secret changes, Fleet doesn't detect this and still shows my bundle as in sync. Even when I hit force update, the old values are redeployed, as the BundleDeployment does not update. I need to change something in my bundle to force Fleet to reread the referenced secret.

This is especially unsatisfying as this specific secret is automatically generated by the External Secrets Operator.

Expected Behavior

Fleet should detect that the values from a referenced Secret/ConfigMap change and redeploy the Bundle if needed.

Steps To Reproduce

1. Create a Fleet Bundle and reference Helm values from a Secret or ConfigMap
2. Deploy the Bundle
3. Change the values in the Secret/ConfigMap
4. Nothing happens

Environment

- Architecture: amd64
- Fleet Version: 0.9.0
- Cluster:
  - Provider: RKE2
  - Options:
  - Kubernetes Version: 1.26.12

Logs

No response

Anything else?

No response

[schakko]

+1