Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Modify grpc web socket address to route through ingress #37021

Open
dingyiyi0226 opened this issue Nov 7, 2024 · 0 comments
Open

Modify grpc web socket address to route through ingress #37021

dingyiyi0226 opened this issue Nov 7, 2024 · 0 comments
Labels
triage Issue requires triage

Comments

@dingyiyi0226
Copy link

Title: Modify grpc web socket address to route through ingress

Description:

For the gRPC-web implementation, the socket address and port are currently set to the name and port of the gRPC service. I would like to wrap this service within the ingress. Is this configuration possible?
I attempted to set it up but encountered a “404 Not Found” error.

The original configuration is similar to this example
and change the following lines

 - lb_endpoints:
  - endpoint:
     address:
       socket_address:
-         address: grpc-svc
-         port_value: 12345
+         address: abc.com
+         port_value: 80

The ingress configuration

apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
  name: abc
  labels:
    app.kubernetes.io/name: abc
  annotations:
    external-dns.alpha.kubernetes.io/hostname: abc.com
    kubernetes.io/ingress.class: traefikclass
    traefik.ingress.kubernetes.io/router.entrypoints: web
spec:
  rules:
    - host: abc.com
      http:
        paths:
          - path: /some.Endpoint
            pathType: Prefix
            backend:
              service:
                name: grpc-svc
                port:
                  number: 12345
@dingyiyi0226 dingyiyi0226 added the triage Issue requires triage label Nov 7, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
triage Issue requires triage
Projects
None yet
Development

No branches or pull requests

1 participant