-
Notifications
You must be signed in to change notification settings - Fork 101
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
[DO NOT MERGE] Test upgrade gateway API to v1.0.0-rc2 #1169
Conversation
If we create a v1beta1 Gateway resource in k8s, does our controller still process it? Thinking of backwards compatibility. |
@sjberman Yep, I tested both v1 and v1beta1 resource manifests when deploying the examples (it's mentioned in the PR description but I might not have been very clear 😆) |
@ciarams87 Oh thanks, I brushed through the description too fast! |
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.
checked all examples work (using both v1beta1 and v1 manifests)
nice! thanks for thorough testing 👍
@@ -48,7 +48,6 @@ load-images: ## Load NGF and NGINX images on configured kind cluster | |||
.PHONY: prepare-ngf-dependencies | |||
prepare-ngf-dependencies: update-ngf-manifest ## Install NGF dependencies on configured kind cluster | |||
./scripts/install-gateway.sh $(GW_API_VERSION) | |||
kubectl wait --for=condition=available --timeout=60s deployment gateway-api-admission-server -n gateway-system |
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.
what is the reason for removing wait here and in ci.yaml?
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.
It was a quick fix for testing purposes - they removed default installation of Gateway API admission server and related resources (because of the move to using CEL validation instead). We'll actually want to update to optionally install these resources for cases where the k8s version is <1.26. See kubernetes-sigs/gateway-api#2400
@@ -62,7 +62,7 @@ const ( | |||
// | |||
// FIXME(bjee19): Update to Gateway sig v1 version when released. | |||
// https://github.com/nginxinc/nginx-gateway-fabric/issues/1168 | |||
RouteConditionPartiallyInvalid v1beta1.RouteConditionType = "PartiallyInvalid" | |||
RouteConditionPartiallyInvalid v1.RouteConditionType = "PartiallyInvalid" |
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.
Could we also update to https://github.com/kubernetes-sigs/gateway-api/blob/adbd9968d4ff7995af21cb9cd0913288e2b4ca27/apis/v1/shared_types.go#L435 and remove the FIXME?
c48536f
to
3e26a99
Compare
f705780
to
17dd272
Compare
b2a64e2
to
c5b0b98
Compare
335a253
to
307814d
Compare
307814d
to
9077476
Compare
Proposed changes
Problem:
Uncertainty if an upgrade Gateway API v1.0.0-rc2 breaks anything
Solution:
Testing:
Ran unit-tests, conformance tests, and checked all examples work (using both v1beta1 and v1 manifests)
One conformance test is failing -
TestConformance/GatewayWithAttachedRoutes/Gateway_listener_should_have_AttachedRoutes_set_even_when_Gateway_has_unresolved_refs
. We have a ticket to address this: #1148 .Note: ReferenceGrant is not moving to v1 with this bump
Note: As I mostly did a copy and replace of a lot of the v1beta1 references in the code, many of the docs changes etc are also included here. We can hopefully use this branch as a starting point when we do bump to v1.
Closes #1144
Checklist
Before creating a PR, run through this checklist and mark each as complete.