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

Add ForceSemverUpgradeConstraints feature gate #395

Closed
m1kola opened this issue Sep 5, 2023 · 0 comments · Fixed by #438
Closed

Add ForceSemverUpgradeConstraints feature gate #395

m1kola opened this issue Sep 5, 2023 · 0 comments · Fixed by #438
Assignees
Milestone

Comments

@m1kola
Copy link
Member

m1kola commented Sep 5, 2023

Please read RFC for better formatting and full scope. The excerpt below is just to indicate the scope covered by this specific issue.

We need to implement a feature gate as per RFC:

Need a feature gate to switch between two upgrade constraint semantics. When:

  • Disabled - operator-controller uses legacy semantics
  • Enabled (default) - operator-controller uses semver

The feature gate can be enabled or disabled by passing the following flag to the manager binary:

--feature-gates=ForceSemverUpgradeConstraints=true

This functionality will be built on top of operator-controller’s existing feature gate mechanisms which is based on the k8s.io/component-base/featuregate package.

@joelanford joelanford added this to the v0.6.0 milestone Sep 14, 2023
@dtfranz dtfranz modified the milestones: v0.6.0, v0.7.0 Oct 3, 2023
@m1kola m1kola self-assigned this Oct 5, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Archived in project
Development

Successfully merging a pull request may close this issue.

3 participants