-
Notifications
You must be signed in to change notification settings - Fork 7.6k
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
[release-1.19] Update sigs.k8s.io/gateway-api to 0.8.0 #46677
Conversation
Hold for 1.19.1 |
Since we need to cut a new rc for #46706, do we want to go ahead and merge this too? |
Those changes were just for the Edit to add: Saw discussion on other PRs. Let's move to slack. |
7594de8
to
c2073df
Compare
Pulled in changes from #46773 for moving to the actual 0.8.0 release. |
It looks like you missed the |
Yep. Looks like that came in a late commit. Pulling that as well. |
go.mod
Outdated
@@ -108,19 +108,19 @@ require ( | |||
gopkg.in/yaml.v2 v2.4.0 | |||
gopkg.in/yaml.v3 v3.0.1 | |||
helm.sh/helm/v3 v3.12.2 | |||
istio.io/api v1.19.0-rc.0.0.20230828012244-464da4944bb2 | |||
istio.io/api v1.19.0-beta.1.0.20230821193953-6d232ba686ad |
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 think now this can be updated to v1.19.0
?
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 believe there is a PR to do the that was put on hold.
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.
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.
Once that PR merges, the pipeline will push the change to istio/istio.
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.
Thanks for the info
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.
Once that PR merges, the pipeline will push the change to istio/istio.
Or since the pipeline was held, we may find we have a rebase issue, and have to fix it manually. Will know more once these PRs start getting approved/un held.
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.
@ericvn I think one thing may not be correct is the istio/api
repo's version is changed from rc
to beta
b44c8e8
to
87bbbae
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, I think I saw the operator/
and test/
changes in the main branch which was also related to the gateway-api bumping.
The label is typically not indicative of much as the pipeline keeps things in check. At the time this was done, that was likely the correct up-repo commit that matched across repos. But I see something else merged and caused another rebase-needed. Likely an up-repo change merged and got pushed down and I need to pick that up (I suspect it will be the upstream repos moving from beta-> rc necessitating your desired change in this PR). |
104b7cf
to
7a0a25e
Compare
Rebased and should be good again. All the repos got back in sync with the build-tools common-files updates across the repos so this PR no longer contains updates in api and client-go. |
Letting this merge to prevent any more required rebases and 1.19.0 has been released and this can merge for 1.19.1. |
Please provide a description of this PR:
This is a manual cherry-pick of #46674 which is a subset of a larger #46658. We don't want to pull all the changes in (I don't think), so this limits to just the gateway-api.
To help us figure out who should review this PR, please put an X in all the areas that this PR affects.