Skip to content

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

@m1kola

Description

@m1kola

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.

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentationhelp wantedDenotes an issue that needs help from a contributor. Must meet "help wanted" guidelines.kind/documentationCategorizes issue or PR as related to documentation.lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions