I believe GRPC is actually already supported, but it doesn't appear in the documentation. I'll test and report back.
this appears to have created an ingress successfully:
apiVersion: extensions/v1beta1
kind: Ingress
metadata:
annotations:
alb.ingress.kubernetes.io/certificate-arn: <REDACTED>
alb.ingress.kubernetes.io/listen-ports: '[{"HTTP": 80}, {"HTTPS":443}]'
alb.ingress.kubernetes.io/actions.ssl-redirect: '{"Type": "redirect", "RedirectConfig": { "Protocol": "HTTPS", "Port": "443", "StatusCode": "HTTP_301"}}'
alb.ingress.kubernetes.io/scheme: internal
alb.ingress.kubernetes.io/ssl-passthrough: "true"
alb.ingress.kubernetes.io/target-type: ip
alb.ingress.kubernetes.io/backend-protocol-version: GRPC
alb.ingress.kubernetes.io/healthcheck-protocol-version: GRPC
kubernetes.io/ingress.class: alb
name: argocd-server-grpc
namespace: argocd
spec:
rules:
- http:
paths:
- backend:
serviceName: ssl-redirect
servicePort: use-annotation
path: /*
- backend:
serviceName: argocd-server
servicePort: 8080
path: /*
However, it appears the Target Groups don't reflect the protocol version as GRPC
@ghostsquad
Hi, the GRPC support will be released as part of our v2.1.0 release soon. stay tuned.
closing this as v2.1.0 is released :D
Most helpful comment
closing this as v2.1.0 is released :D