Skip to content

Remove ForceSemverUpgradeConstraints feature gate and implementation #1615

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
joelanford opened this issue Jan 14, 2025 · 0 comments · Fixed by #1638
Closed

Remove ForceSemverUpgradeConstraints feature gate and implementation #1615

joelanford opened this issue Jan 14, 2025 · 0 comments · Fixed by #1638

Comments

@joelanford
Copy link
Member

We added this feature gate very early in operator-controller's development as a shortcut to generate upgrade edges based on server, while ignoring the legacy upgrade edges (replaces/skip/skipRange). Now that operator-controller understands the legacy upgrade edges, there is no real reason to ever use the ForceSemverUpgradeConstraints feature gate because it ignores extension author intent.

Let's remove the feature gate and the code that it enables.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
1 participant