-
Notifications
You must be signed in to change notification settings - Fork 14
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
THREESCALE-10869 Bump Go, controller-runtime, and k8s dependencies #208
Conversation
864bf3c
to
8d6c527
Compare
/retest |
cc9106e
to
a9de498
Compare
a9de498
to
0b24bff
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.
overall looks good, some changes requested but I could be wrong
My main concern is the upgrade of controller-runtime beyond v0.15.0 as v0.15.0 introduced large list of breaking changed. I review them and nothing caught my eye. But second pair of 👁️ would be very nice https://github.com/kubernetes-sigs/controller-runtime/releases/tag/v0.15.0 |
@eguzki I reviewed every breaking change for every version from v0.12.2 to v0.16.5 and cross referenced them with the source code to ensure we weren't affected (or I included the fix to support the breaking change if we were affected). I did this when performing the 3scale-operator bump as well. That being said, more eyes reviewing it is always a good thing. |
1724609
to
1e43754
Compare
this is getting pretty close to be merged. Just one iteration more with few comments and we should be ready to merge. |
1e43754
to
26cc8af
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.
good job! 🏅
Issue Link
JIRA: THREESCALE-10869
What
This PR bumps a number of dependencies, the notable ones being:
go: 1.19 -> 1.20
ginkgo: 1.16.5 -> 2.13.0
client-go: 0.24.3 -> 0.28.3
apimachinery: 0.24.3 -> 0.28.3
controller-runtime: 0.12.2 -> 0.16.5
NOTE: This PR doesn't bump the version of
operator-sdk
, that will be done in a separate PR.Verification Steps
Prerequisites
Cluster Scoped Scenario
oc get apicast -n $NAMESPACE -o yaml -w
curl 127.0.0.1:8080/test -H "Host: localhost"
oc delete project $NAMESPACE
Namespace Scoped Scenario
Navigate to the
OperatorHub
in the OpenShift UI, search forapicast
, and install the dev version the apicast-operator in theapicast-test
Namespace.Verify the installation completes successfully:
oc get apicast -n $NAMESPACE -o yaml -w
curl 127.0.0.1:8080/test -H "Host: localhost"