Skip to content

Commit

Permalink
docs(ingress): use GRPC instead of HTTP2 (#21029)
Browse files Browse the repository at this point in the history
Signed-off-by: Alexandre Gaudreault <alexandre_gaudreault@intuit.com>
  • Loading branch information
agaudreault authored Dec 3, 2024
1 parent bd5d76f commit 205b3d3
Showing 1 changed file with 2 additions and 2 deletions.
4 changes: 2 additions & 2 deletions docs/operator-manual/ingress.md
Original file line number Diff line number Diff line change
Expand Up @@ -415,7 +415,7 @@ apiVersion: v1
kind: Service
metadata:
annotations:
alb.ingress.kubernetes.io/backend-protocol-version: HTTP2 #This tells AWS to send traffic from the ALB using HTTP2. Can use GRPC as well if you want to leverage GRPC specific features
alb.ingress.kubernetes.io/backend-protocol-version: GRPC # This tells AWS to send traffic from the ALB using GRPC. Plain HTTP2 can be used, but the health checks wont be available because argo currently downgrade non-grpc calls to HTTP1
labels:
app: argogrpc
name: argogrpc
Expand Down Expand Up @@ -454,7 +454,7 @@ Once we create this service, we can configure the Ingress to conditionally route
- path: /
backend:
service:
name: argogrpc
name: argogrpc # The grpc service must be placed before the argocd-server for the listening rules to be created in the correct order
port:
number: 443
pathType: Prefix
Expand Down

0 comments on commit 205b3d3

Please sign in to comment.