Skip to content

Respect .spec.upgradeConstraintPolicy #449

Closed
@m1kola

Description

@m1kola

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

Need to update code to respect .spec.upgradeConstraintPolicy accordingly to the RFC:

When .spec.upgradeConstraintPolicy is set to Ignore we do not apply upgrade constraints. This means an Operator can be transitioned to any available version of the package (even one older than the currently installed one). Note that, if set, other constraints on Operator still apply (e.g. .spec.version and .spec.channel).

When .spec.upgradeConstraintPolicy is set to Enforce we use either semver or legacy semantics depending on the position of the ForceSemverUpgradeConstraints feature gate.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type

Projects

Status

Done

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions