Skip to content

Solver: Introduce constraints for "upgrade edges" #267

Closed

Description

@jmprusi

For an operator upgrade to be valid, the new operator version should comply with a set of constraints:

  • Channel: The new operator version should be part of the same channel
  • Replaces: The currently installed operator version should be included in the "replace" field of the new desired operator version (see skips)
  • Skips: Skips define from what version it is possible to jump to without upgrading one version at a time. This should be considered and not only the "replaces" field.

related to #231

Activity

  1. moved this to In Progress in OLM v1on Jun 22, 2023
  2. joelanford commented on Jun 27, 2023

    @joelanford
    Member

    Channel: The new operator version should be part of the same channel

    This is a anti-goal. This would prohibit upgrades between channels even when there is an upgrade edge from the currently installed version defined in the new channel (and the user is not opposed to using that channel)

  3. joelanford commented on Jun 27, 2023

    @joelanford
    Member
  4. moved this from In Progress to Done in OLM v1on Aug 3, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

Labels

Type

No type

Projects

  • Status
    Done

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions