Skip to content
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

feat(api): add native clusterselector #312

Merged
merged 2 commits into from
Jun 12, 2024

Conversation

oliverbaehler
Copy link
Contributor

@oliverbaehler oliverbaehler commented Jun 12, 2024

@@ -71,6 +72,10 @@ var (

type Selector string

type ClusterSelector struct {
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Do you envision depracating the old Selector few releases after we introduce new type? Or taking care of that on upgrade by moving to v1beta1 for instance?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, I don't know how you would like to handle crd lifecycles. For me its always new additions are okay on the same api version. Removal on the next api version bump. So i would suggest the second option

Copy link
Member

@gianlucam76 gianlucam76 Jun 12, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you. I have been thinking to move to v1beta1 for some time now (I think two years is more than enough to justify such change). I guess we can do while introducing this feature (and I will help of course).

Saying that just so we only have one way to select a set of clusters (the new ClusterSelector you are introducing) so it is not confusing. And while also not breaking existing deployment (handful of companies are using Sveltos in production).

@gianlucam76 gianlucam76 merged commit f66e954 into projectsveltos:dev Jun 12, 2024
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants