-
Notifications
You must be signed in to change notification settings - Fork 16
gateway-api: update to v0.5.0 and v1beta1 resources #224
Conversation
0e311a5
to
b5f685e
Compare
Moving |
bc5ce1f
to
40c4b64
Compare
@@ -2,6 +2,7 @@ apiVersion: kustomize.config.k8s.io/v1beta1 | |||
kind: Kustomization | |||
|
|||
resources: | |||
- github.com/kubernetes-sigs/gateway-api/config/crd?ref=v0.4.1 | |||
- github.com/kubernetes-sigs/gateway-api/config/crd/experimental?ref=v0.5.0-rc1 | |||
- https://raw.githubusercontent.com/kubernetes-sigs/gateway-api/v0.5.0-rc1/config/crd/experimental/gateway.networking.k8s.io_referencepolicies.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.
Needed to be installed explicitly because kustomize seems to omit the ReferencePolicies CRD by default due to it being marked deprecated: true
. Remote resource install refs kubernetes-sigs/kustomize#970 (comment)
6ddb9b4
to
3375eb3
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.
This is looking good! Would like to get merged this week to let it bake for as long as possible while we build up to our v0.4.0 release.
I haven't done so yet but want to make sure we have a ticket for upgrading HTTPRoute to v1beta1. It seems like something we could easily overlook ahead of our release if we don't, and I'd like to be as up-to-date as possible with kubernetes-sigs/gateway-api by our next release.
.github/workflows/conformance.yml
Outdated
uses: actions/checkout@v2 | ||
with: | ||
repository: "hashicorp/consul-k8s" | ||
ref: "charts/capigw-controller-clusterrole-referencegrants" |
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.
Note: this branch is from hashicorp/consul-k8s#1299
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.
Since the PR above is so small, it'd be nice if we could merge it first and then have this PR reference main
.
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.
Closing the loop: hashicorp/consul-k8s#1299 (comment) resulted in the conclusion that we don't want to merge the above PR just yet.
Are you thinking we move ahead with this PR and just leave the with.ref
pointed at the branch above @mikemorris ?
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.
Yea, I think that could be reasonable to avoid this getting stale, will open an issue tracking that so we don't forget.
|
to match envtest requirements
k8s/controllers: minor refactor and mocking up future ReferencePolicy support for backwards compatibility k8s/gatewayclient: regenerate mocks after ReferenceGrant rename docs: update supported-features.md for ReferenceGrant k8s/controller: update http and tcp route controller tests for ReferenceGrant k8s/reconciler: update listener test for ReferenceGrant k8s/reconciler: update route test for ReferenceGrant e2e: update ReferencePolicy -> ReferenceGrant k8s/reconciler: update utils test for ReferenceGrant k8s/reconciler: update statuses for ReferenceGrant rbac: add gateway controller permissions to read ReferenceGrants
… CRDs e2e: rename kubectlKustomizeCRDs arg from url to path
e2e/kubernetes: add v1beta1 known types separately from v1alpha2 known types
1e24ace
to
7b158cd
Compare
…tes and ReferenceGrant gateway-api: add ReferencePolicy backwards compatibility support mocks: regenerate k8s/controller: add gwv1alpha2 to scheme k8s/gatewayclient: add gwv1alpha2 to scheme for test helpers
8f2ac73
to
09fede1
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.
Just the one last thing; otherwise LGTM
Changes proposed in this PR:
Before merging, this should be updated to [email protected]Update all v1alpha1 references to v1alpha2 if not graduated to v1beta1 yet"github.com/hashicorp/consul-api-gateway/pkg/apis/v1alpha1"
v1beta1
forHTTPRoute
for now due to the complications of shared logic with other route types still onv1alpha2
ReferencePolicy
How I've tested this PR:
Notes for reviewers:
go.mod
updates to k8s.io modules are due to deps: update k8s.io modules to v0.24 kubernetes-sigs/gateway-api#1199 which switches fromgoogleapis/gnostic
togoogle/gnostic
- this was handled in Update kubectl kustomize to v4.5.4 kubernetes/kubernetes#108994 to resolve the dependency conflict, but requires updating all dependencies in lockstepinternal/k8s/logger.go
changes are to adapt to the breaking change in Rearch for performance: BREAKING CHANGES go-logr/logr#42 hit due to the dependency bump to go-logr/logr from updating the Kubernetes ecosystem librariesv1beta1.CommonRouteSpec
orv1alpha2.CommonRouteSpec
depending on the route type) - wanted to keep that out of scope for now to avoid excessive complexity/refactoring.How I expect reviewers to test this PR:
Verify that the changes seems sensible and nothing was missed.
Checklist:
ReferencePolicy
backwards compatibility supportGateway controller certificateRefse2e