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
The TeamRoleBinding currently supports either ClusterName or ClusterSelector1 to determine the relevant clusters.
With the implementation of #724 these can be combined into the new Type ClusterSelector. In order to not break existing resources there needs to be a new v1alpha2 Version of the TeamRoleBinding that has a conversion webhook that is able to transform between the two without breaking. see https://book.kubebuilder.io/multiversion-tutorial/tutorial
Acceptance Criteria
New v1alpha2 Version of TeamRoleBinding using the new ClusterSelector type
Converson between v1alpha1 and v1alpha2
Reference Issues
No response
The text was updated successfully, but these errors were encountered:
Priority
None
User Story
No response
Description
The TeamRoleBinding currently supports either
ClusterName
orClusterSelector
1 to determine the relevant clusters.With the implementation of #724 these can be combined into the new Type
ClusterSelector
. In order to not break existing resources there needs to be a newv1alpha2
Version of the TeamRoleBinding that has a conversion webhook that is able to transform between the two without breaking. see https://book.kubebuilder.io/multiversion-tutorial/tutorialAcceptance Criteria
ClusterSelector
typeReference Issues
No response
The text was updated successfully, but these errors were encountered: