fleet: [SURE-5668] Fleet BundleDeployments does not reflect new labels from Bundles

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

If we update an existing Fleet Bundle with additional labels then we can observe that BundleDeployments do not have the newly added labels unless we either:

  • Delete the Bundle
  • Manually patch the BundleDeployment in the cluster’s Fleet namespace in the local cluster

This is problematic as we iterate on our Fleet deployments and leveraging the dependsOn feature. The dependent BundleDeployment will say this until we patch the BundleDeployment object with the new label.

No bundles matching labels x=y in namespace fleet-default

Expected Behavior

We expect BundleDeployments to be a reflection of Bundle objects, including from labels and annotations updates.

Steps To Reproduce

  1. Create GitRepo A object with labels a=b inside fleet.yaml.
  2. Observe Bundle and BundleDeployment objects created with labels a=b
  3. Update GitRepo A with a new label x=y by updating fleet.yaml
  4. Create second GtiRepo B object that dependsOn the GtiRepo A with the label x=y inside of fleet.yaml.
  5. See that the cluster’s BundleDeployment object from GitRepo B display this error:
No bundles matching labels x=y in namespace fleet-default
  1. Manually patch BundleDeployment object from GitRepo A with label x=y (or delete Bundle objecet from GitRepo A but this is not ideal as this will cause the application to be reinstalled).

Environment

- Architecture: amd
- Fleet Version: 0.5.0
- Cluster:
  - Provider: RKE, RKE2, K3S
  - Kubernetes Version: v1.21.x

Logs

No response

Anything else?

No response

About this issue

  • Original URL
  • State: closed
  • Created 2 years ago
  • Comments: 15 (7 by maintainers)

Most upvoted comments

Can we also add the following test scenarios after it’s been deployed?

  1. Removing a label
  2. Adding a new label