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

Grpc Load Balancing not working #633

Open
metalLeveller opened this issue Sep 7, 2022 · 0 comments
Open

Grpc Load Balancing not working #633

metalLeveller opened this issue Sep 7, 2022 · 0 comments
Labels
bug Something isn't working

Comments

@metalLeveller
Copy link

metalLeveller commented Sep 7, 2022

Describe the bug
GRPC Load Balancing is not working for several pods in one service. VirtualRouter is sending all requests to only one pod.

Steps to reproduce
Create two services (let's call them A and B), with one service (A) receiving traffic from outside world, and invoking GRPC method on the other service (B). Create multiple pods for service B.

Expected outcome
Traffic should be equally distributed between pods of service B.

Environment

  • App Mesh controller version: appmesh-controller:v1.6.0
  • Envoy version: aws-appmesh-envoy:v1.22.2.1-prod
  • Are you using any integrations? No
  • Kubernetes version: 1.23
  • Using EKS (yes/no), if so version? yes, 1.23

Additional Context:
Looks like duplicate, but that solution didn't work.

Confurigations:

kind: VirtualService
metadata:
  name: user-service
  namespace: app
spec:
  awsName: user-service.app.svc.cluster.local
  provider:
    virtualRouter:
      virtualRouterRef:
        name: user-service-virtual-router
kind: VirtualRouter
metadata:
  namespace: app
  name: user-service-virtual-router
spec:
  listeners:
    - portMapping:
        port: 6565
        protocol: grpc
  routes:
    - name: user-service-route
      httpRoute:
        match:
          prefix: /
        action:
          weightedTargets:
            - virtualNodeRef:
                name: user-service
              weight: 1
kind: VirtualNode
metadata:
  name: user-service
  namespace: app
spec:
  podSelector:
    matchLabels:
      app: user-service
  listeners:
    - portMapping:
        port: 6565
        protocol: grpc
  serviceDiscovery:
    awsCloudMap:
      namespaceName: app
      serviceName: user-service

We were trying to use different configurations for service discovery:

    dns:
      hostname: user-service.app.svc.cluster.local
@metalLeveller metalLeveller added the bug Something isn't working label Sep 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

1 participant