-
Notifications
You must be signed in to change notification settings - Fork 594
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
fix: Use only 46 bits for priorities of generated Kong routes #5010
Conversation
E2E (targeted) tests with KIND-based clusters were started at https://github.com/Kong/kubernetes-ingress-controller/actions/runs/6690809874 |
Codecov ReportAttention:
Additional details and impacted files@@ Coverage Diff @@
## main #5010 +/- ##
=====================================
Coverage 72.9% 73.0%
=====================================
Files 167 167
Lines 18719 18718 -1
=====================================
+ Hits 13654 13666 +12
+ Misses 4233 4223 -10
+ Partials 832 829 -3
☔ View full report in Codecov by Sentry. |
@@ -56,7 +56,7 @@ require ( | |||
k8s.io/client-go v0.28.3 | |||
k8s.io/component-base v0.28.3 | |||
sigs.k8s.io/controller-runtime v0.16.3 | |||
sigs.k8s.io/gateway-api v1.0.0-rc2 | |||
sigs.k8s.io/gateway-api v1.0.0-rc2.0.20231027061746-5fd8bec3bedc |
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.
Let's not bump this in a PR not related to Gateway 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.
I checked out to the branch from another branch to update the conformance tests. I will make another PR from main branch and close this.
What this PR does / why we need it:
Which issue this PR fixes:
fixes #5009
Special notes for your reviewer:
PR Readiness Checklist:
Complete these before marking the PR as
ready to review
:CHANGELOG.md
release notes have been updated to reflect any significant (and particularly user-facing) changes introduced by this PR