Open wimnat opened 6 months ago
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
/remove-lifecycle stale
As replied to in the sig-network-gateway-api thread by @candita , GRPCRoute's interaction with BackendTLSPolicy is currently implementation dependent (https://gateway-api.sigs.k8s.io/geps/gep-1897/#how-a-client-behaves)
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
lifecycle/stale
is appliedlifecycle/stale
was applied, lifecycle/rotten
is appliedlifecycle/rotten
was applied, the issue is closedYou can:
/remove-lifecycle stale
/close
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
What would you like to be added:
In GEP-1897, the document states:
Now that
GPRCRoute
has graduated to v1 , I think that it should be possible to add aBackendTLSPolicy
that matches onGRPCRoute
objects.Why this is needed:
Without this change, any GRPC service that is running with a TLS enabled port can not be accessed via a
GPRCRoute
and instead the user must fall back to using anHTTPRoute
resource with the appropriateBackendTLSPolicy
.Also discussed in Slack here