deploy: use traefik for grpc https #2598
Merged
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.
Updates the cluster deployment logic to use
IngressRoute
, rather thanIngress
, for managing HTTPS traffic. TheIngressRoute
CRD is specific to Traefik on k8s [0]. We use it specifically to leverage h2c support, so we can terminate TLS at the proxy layer, then pass plaintext HTTP traffic to the gRPC backend for pd. Traefik now serves to manage HTTPS connections for the other ingressed services, such as Tendermint RPC over HTTPS, and the Grafana dashboard over HTTPS.[0] https://doc.traefik.io/traefik/routing/providers/kubernetes-crd/#kind-ingressroute begin porting ingress obj