Skip to content

Conversation

@gallettilance
Copy link
Contributor

@gallettilance gallettilance commented Aug 6, 2024

DEMO

maxopenshiftversionDEMO.mp4

@openshift-ci openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Aug 6, 2024
@openshift-ci openshift-ci bot requested review from grokspawn and m1kola August 6, 2024 16:26
@gallettilance gallettilance force-pushed the ocpmaxversion branch 3 times, most recently from b662c6c to 7682012 Compare September 3, 2024 17:25
OwnerKindKey = "olm.operatorframework.io/owner-kind"
OwnerNameKey = "olm.operatorframework.io/owner-name"
PackageNameKey = "olm.operatorframework.io/package-name"
BundleNameKey = "olm.operatorframework.io/bundle-name"
BundleVersionKey = "olm.operatorframework.io/bundle-version"
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Probably makes sense to define these in the o-c API.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

will create a PR

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@gallettilance I will recommend to create an upstream issue (in operator-controller) before creating a PR.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

For anything not being moved to operator-controller (e.g. MaxOpenShiftVersionProperty), we should unexport it since we don't intend for it to be used outside this package.

} else {
// Incompatible
name := rel.Labels[BundleNameKey]
incompatibleOperators = append(incompatibleOperators, name)
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I know this would differ from OLMv0, but it might be nice to include the name of the ClusterExtension somehow in the error message, which would give users a breadcrumb to the object they need to change in order to resolve this condition.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

agreed - let's create a new ticket to track that addition and I can create a follow up PR

@gallettilance
Copy link
Contributor Author

/hold until openshift/library-go#1771 merges

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Sep 11, 2024
@gallettilance gallettilance force-pushed the ocpmaxversion branch 2 times, most recently from 4305d57 to 6f0430f Compare September 11, 2024 17:44
@gallettilance gallettilance changed the title WIP: (feat) block cluster upgrade when installed operators have a max ocp version set that is incompatible with the next minor release (feat) block cluster upgrade when installed operators have a max ocp version set that is incompatible with the next minor release Sep 11, 2024
@gallettilance gallettilance force-pushed the ocpmaxversion branch 3 times, most recently from 2ed9388 to d22cf18 Compare October 1, 2024 19:27
@joelanford
Copy link
Member

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 3, 2024
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Oct 3, 2024

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: gallettilance, joelanford

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 3, 2024
@openshift-merge-bot openshift-merge-bot bot merged commit 2c36793 into openshift:main Oct 3, 2024
5 checks passed
@openshift-bot
Copy link

[ART PR BUILD NOTIFIER]

Distgit: ose-cluster-olm-operator
This PR has been included in build ose-cluster-olm-operator-container-v4.18.0-202410040142.p0.g2c36793.assembly.stream.el9.
All builds following this will include this PR.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. lgtm Indicates that a PR is ready to be merged.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

8 participants