We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
ForceSemverUpgradeConstraints
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.
Need a feature gate to switch between two upgrade constraint semantics. When:
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.
The text was updated successfully, but these errors were encountered:
m1kola
Successfully merging a pull request may close this issue.
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:
The text was updated successfully, but these errors were encountered: