Skip to content

Utilizing Label Selectors #50

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
csviri opened this issue Apr 1, 2024 · 0 comments · Fixed by #86
Closed

Utilizing Label Selectors #50

csviri opened this issue Apr 1, 2024 · 0 comments · Fixed by #86
Labels
enhancement New feature or request
Milestone

Comments

@csviri
Copy link
Collaborator

csviri commented 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 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.

@csviri csviri changed the title Label selectors for Glue and Glue Label selectors for Glue and Glue Operator Apr 1, 2024
@csviri csviri changed the title Label selectors for Glue and Glue Operator Utilizing Label selectors Apr 1, 2024
@csviri csviri changed the title Utilizing Label selectors Utilizing Label Selectors Apr 1, 2024
@csviri csviri added this to the 0.2.0 milestone Apr 1, 2024
@csviri csviri added the enhancement New feature or request label Apr 2, 2024
@csviri csviri linked a pull request Apr 26, 2024 that will close this issue
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant