Backport of [NET-7657,NET-6934] Define v2 GatewayClass + GatewayClassConfig locally into release/1.4.x #3572
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Backport
This PR is auto-generated from #3559 to be assessed for backporting due to the inclusion of the label backport/1.4.x.
The below text is copied from the body of the original PR.
Changes proposed in this PR
The
spec
field for v2GatewayClass
es currently uses the proto-public definitions from Consul; however, we don't want to do that anymore since Consul has no need for this type at all.We've already broken this dependency for
GatewayClassConfig
in the past but need to do the same forGatewayClass
so that we can remove the proto definition from Consul altogether.How I've tested this PR
helm install
with.meshGateway.enabled=true
and.global.imageK8S
set to the build of this branchHow I expect reviewers to test this PR
See above
Checklist
Overview of commits