You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
As a user I would like to reapply resources when I update underlying ResourceReference secret or configmap data
Detailed Description
I am capv operator and I deploy CNI and CSI using clusterresourceset,
now using applyonce strategy capi ensures that these
resources are applied to cluster once
But if I change/update say CSI image tags for newer release the resources will not be updated
I would like to update my resources on such changes
So I propose to implement a new Strategy for ClusterResourceSet UpgradeOnChange
UpgradeOnChange behaves like ApplyOnce on first creation
and later if there are changes in the contents of ResourceReference
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
/kind feature
The text was updated successfully, but these errors were encountered:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
User Story
As a user I would like to reapply resources when I update underlying ResourceReference secret or configmap data
Detailed Description
I am capv operator and I deploy CNI and CSI using clusterresourceset,
now using applyonce strategy capi ensures that these
resources are applied to cluster once
But if I change/update say CSI image tags for newer release the resources will not be updated
I would like to update my resources on such changes
So I propose to implement a new Strategy for ClusterResourceSet UpgradeOnChange
UpgradeOnChange behaves like ApplyOnce on first creation
and later if there are changes in the contents of ResourceReference
Anything else you would like to add:
[Miscellaneous information that will assist in solving the issue.]
/kind feature
The text was updated successfully, but these errors were encountered: