-
Notifications
You must be signed in to change notification settings - Fork 32
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
Istio (v1.17.2) and Gateway API (v0.6.2) version bump #166
Conversation
Bump version of Istio used for local dev and testing to 1.17.2.
This is failing because of this: istio/istio.io#12630 (comment) I.e. the second gateway created by the integration test case at kuadrant-operator/controllers/authpolicy_controller_test.go Lines 42 to 43 in 5af4c71
won't be ready, thus failing at this check that is performed by the controller when the kuadrant-operator/pkg/reconcilers/targetref_reconciler.go Lines 55 to 57 in 5af4c71
Update: Adding here a couple more refs: |
Updates sigs.k8s.io/gateway-api to v0.6.2. Co-dependencies updated: - sigs.k8s.io/controller-runtime (v0.14.6) - go.uber.org/zap (v1.24.0)
This seems to be making the same change to the gateway-api module as #153, but with far fewer changes. I think it's because you haven't changed the api version to v1beta1 #153 (comment). DO we not want to do that? |
Focus here started on upgrading Istio. I ended bringing GWAPI v0.6 together due to dependencies. With many CRDs now promoted to beta, I believe we do want to upgrade them in our code base as well. Perhaps an obvious consecutive step then would be rebasing and merging #153, right after this PR? Or you'd say it better done all at once as part of the same iteration? Either way works for me. To have in mind that having Istio up to date is also important before moving to GWAPI v0.6.2. And related to that, this PR also fixes the status check of Gateway objects – from using |
Yeah, lets just merge this and I'll update my PR to just update the api version we are using. |
I've tested the changes in this PR with a custom build of the operator, bundle and catalog images pushed to quay.io:
The changes worked in both scenarios. In OpenShift, to workaround errors in OSSM related to the GWAPI version, I had to first install an older version of GWAPI and then upgrade it to v0.6.2 after OSSM had successfully started Update: OSSM install failed before due to missing GWAPI CRDs when trying to install v0.6.2 directly with from
|
Other co-dependencies updated: