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
Label selectors could be utilized for different purposes. But one reason is to do sharding for deployment of the operator, so by certain running instances, only selected Glue and GlueOperator resources would be selected.
To achieve this, we can add a label selector field in spec for both resources. GlueOperator would also propagate the label selector to Glue.
It is a question whether we should propagate labels and label selectors automatically for dependent resources. This would be a little problematic if there is a dependent resource and a related resource for the same type, in this case, we create only one informer, and label selectors don't support or.
The text was updated successfully, but these errors were encountered:
csviri
changed the title
Label selectors for Glue and Glue
Label selectors for Glue and Glue Operator
Apr 1, 2024
csviri
changed the title
Label selectors for Glue and Glue Operator
Utilizing Label selectors
Apr 1, 2024
csviri
changed the title
Utilizing Label selectors
Utilizing Label Selectors
Apr 1, 2024
Label selectors could be utilized for different purposes. But one reason is to do sharding for deployment of the operator, so by certain running instances, only selected
Glue
andGlueOperator
resources would be selected.To achieve this, we can add a label selector field in spec for both resources.
GlueOperator
would also propagate the label selector toGlue
.It is a question whether we should propagate labels and label selectors automatically for dependent resources. This would be a little problematic if there is a dependent resource and a related resource for the same type, in this case, we create only one informer, and label selectors don't support
or
.The text was updated successfully, but these errors were encountered: