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

Docs: "Upgrade support" is confusing and doesn't mention a feature gate #1470

Open
m1kola opened this issue Nov 15, 2024 · 1 comment
Open
Assignees
Labels
documentation Improvements or additions to documentation help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/documentation Categorizes issue or PR as related to documentation.

Comments

@m1kola
Copy link
Member

m1kola commented Nov 15, 2024

I think Upgrade support doc requires some rewriting because:

  1. It doesn't mention that the semver upgrades require the ForceSemverUpgradeConstraints feature gate which gives a false impression it is a feature which is enabled by default.
  2. The flow of the document needs improving: going through the doc it is not clear whether SelfCertified and CatalogProvided upgrade constraint policies work with both legacy upgrade edges and server upgrade edges or not.
@m1kola m1kola added documentation Improvements or additions to documentation help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/documentation Categorizes issue or PR as related to documentation. labels Nov 15, 2024
@trgeiger
Copy link
Contributor

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/documentation Categorizes issue or PR as related to documentation.
Projects
None yet
Development

No branches or pull requests

2 participants