Skip to content

Separate Ingress for GRPC #402

Description

@Elyytscha

As you cant really mix GRPC + HTTP Ingresses and the recommendation is to use separate ingresses,

I would recommend or vote for to add a second ingress for grpc

Reference:
kubernetes/ingress-nginx#6269 (comment)

kubernetes/ingress-nginx#10818 (comment)

maybe

ingress:
  enabled: true
  ingressClassName: "nginx"
  additionalLabels: {}
  annotations:
    kubernetes.io/ingress.class: nginx
  hosts:
    - host: qdrant-test.example.com
      paths:
        - path: /
          pathType: Prefix
          servicePort: 6333
  tls:
    - hosts:
      - qdrant-test.example.com

grpcIngress:
  enabled: true
  ingressClassName: "nginx"
  additionalLabels: {}
  annotations:
    kubernetes.io/ingress.class: nginx
    nginx.ingress.kubernetes.io/backend-protocol: "GRPC"
  hosts:
    - host: qdrant-test.example.com
      paths:
        - path: /grpc
          pathType: Prefix
          servicePort: 6334
  tls:
    - hosts:
      - qdrant-test.example.com

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions