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
- Create
GitRepo A
object with labelsa=b
insidefleet.yaml
. - Observe
Bundle
andBundleDeployment
objects created with labelsa=b
- Update
GitRepo A
with a new labelx=y
by updatingfleet.yaml
- Create second
GtiRepo B
object thatdependsOn
theGtiRepo A
with the labelx=y
inside offleet.yaml
. - See that the cluster’s
BundleDeployment
object fromGitRepo B
display this error:
No bundles matching labels x=y in namespace fleet-default
- Manually patch
BundleDeployment
object fromGitRepo A
with labelx=y
(or deleteBundle
objecet fromGitRepo 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)
Can we also add the following test scenarios after it’s been deployed?