-
Notifications
You must be signed in to change notification settings - Fork 12
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
Update operator-sdk to 1.22.1 #135
Update operator-sdk to 1.22.1 #135
Conversation
bundle/manifests/operator-certification-operator.clusterserviceversion.yaml
Outdated
Show resolved
Hide resolved
bundle/manifests/operator-certification-operator.clusterserviceversion.yaml
Outdated
Show resolved
Hide resolved
bundle/manifests/operator-certification-operator.clusterserviceversion.yaml
Outdated
Show resolved
Hide resolved
bundle/manifests/operator-certification-operator.clusterserviceversion.yaml
Outdated
Show resolved
Hide resolved
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.
Added some notes of things I think we may not be intending to change. The changes I noted may have been intentional, but I'm just remembering back to the times where I bump opsdk and have to manually go through and fix these things.
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.
/lgtm
bundle/metadata/dependencies.yaml
Outdated
@@ -2,4 +2,4 @@ dependencies: | |||
- type: olm.package | |||
value: | |||
packageName: openshift-pipelines-operator-rh | |||
version: "1.5.2" | |||
version: "1.7.1" |
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.
We need to test this version with our operator as a bundle/catalog in a net new cluster, to make sure the issues in 1.6.x versions were actually fixed.
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 ran some local tests on a brand-new SNO cluster. I was able to do a pipeline run (the operator I passed itself failed the validation) the pipeline run completed. Would definitely welcome further testing.
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 was able to test this as well, and OCO installed properly, as did operator-pipelines
. I poked the cluster some, events
and logs
from both OLM
operators and didn't see any errors/warns, so I think they fixed all the 1.6.x
issues for the things we care about and need.
bundle/manifests/operator-certification-operator.clusterserviceversion.yaml
Outdated
Show resolved
Hide resolved
@bcrochet: PR needs rebase. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
ecdfaac
to
15ee666
Compare
15ee666
to
450ef5d
Compare
In doing so, this patch also goes back to 1.15.0 (which I think is where we started), and applies all of the migrations that are specified at https://sdk.operatorframework.io/docs/upgrading-sdk-version/ It should be noted that in the future, this should be check every time operator-sdk is updated here. Signed-off-by: Brad P. Crochet <brad@redhat.com>
450ef5d
to
03f03df
Compare
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.
/lgtm
In doing so, this patch also goes back to 1.15.0 (which I think is
where we started), and applies all of the migrations that are specified
at https://sdk.operatorframework.io/docs/upgrading-sdk-version/
It should be noted that in the future, this should be check every
time operator-sdk is updated here.
Signed-off-by: Brad P. Crochet brad@redhat.com