-
Notifications
You must be signed in to change notification settings - Fork 33
OPRUN-3368: block cluster upgrade when installed operators have a max ocp version set that is incompatible with the next minor release #64
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
Conversation
fa30194 to
e466bf7
Compare
b662c6c to
7682012
Compare
| 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" |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
will create a PR
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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) |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
7682012 to
ec07268
Compare
|
/hold until openshift/library-go#1771 merges |
4305d57 to
6f0430f
Compare
676e1f3 to
e553cb4
Compare
e553cb4 to
9463345
Compare
2ed9388 to
d22cf18
Compare
d22cf18 to
a58d280
Compare
a58d280 to
93836bc
Compare
|
/lgtm |
|
[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 |
|
[ART PR BUILD NOTIFIER] Distgit: ose-cluster-olm-operator |
DEMO
maxopenshiftversionDEMO.mp4