zijun726911
commented
5 months ago Could you help me to try this way and let me know does this work for you? (if it's not work, can you help to paste some controller error logs?) Thank you so much! Maybe you can create one HTTPRoute and one GRPCRoute:
apiVersion: gateway.networking.k8s.io/v1beta1
kind: HTTPRoute
metadata:
name: test-application
spec:
hostnames:
- test-app.test.com
parentRefs:
- name: test-service-network
sectionName: rest
namespace: aws-application-networking-system
rules:
- backendRefs:
- name: testapp-service-rest
kind: Service
port: 80apiVersion: gateway.networking.k8s.io/v1alpha2
kind: GRPCRoute
metadata:
name: test-application
spec:
hostnames:
- test-app.test.com
parentRefs:
- name: test-service-network
sectionName: grpc
namespace: aws-application-networking-system
rules:
- backendRefs:
- name: test-app-service-grpc
kind: Service
port: 50051
HannesBBR
Hi,
One of our applications running in k8s accepts both GRPC and HTTP traffic (its pods have different containers with a different port). To handle traffic for this application, we have 2 k8s services:
service-rest=> forwards traffic to the port of the rest-containerservice-grpc=> forwards traffic to the port of the grpc-containerOur current ingress into this k8s application is an ALB with two listeners that forward traffic to the respective k8s service, based on the port:
443listener => forwards to target grouptg-rest, which sends traffic to theservice-restin k8s (targets are managed by the AWS load-balancer controller)50051listener => forwards to target grouptg-grpc, which sends traffic to theservice-grpcin k8s (targets are managed by the AWS load-balancer controller)The domain name used by the clients is the same for both REST and GRPC traffic, and they choose the respective ALB listener port depending on whether they want to talk REST or GRPC.
As we are onboarding services into VPC Lattice, we'd now like the achieve the same kind of setup with VPC Lattice for this application:
443listener => forward all traffic on this port to target groupvpc-lattice-tg-rest50051listener => forward all traffic on this port to target groupvpc-lattice-tg-grpcI have tried some things to achieve this setup using the Gateway API controller, but I didn't find a way to do this:
Two different
HTTPRouteresources with the same name, but a differentsectionNamein theparentRefsproperty and a differentbackendRefservice:=> this creates a single VPC Lattice service with one listener and two target groups. However it causes the controller to periodically flipflop/overwrite the (single) listener of the service between the two ports related to the two
sectionNames, instead of adding a second listener to the service that would then forward traffic to its respective targetgroup.A single
HTTPRouteresource, with twoparentRefsand twobackendRefs:=> the result is a single VPC Lattice service with two listeners, and two target groups. However, the rules in each of the two listeners basically split traffic evenly between the two created target groups, while we'd like to have all traffic for a listener be forwarded to the 'correct' target group only.
Ideally, I would hope something like this would be possible, where you explicitly define which backendRef should be used by which listener/parent:
But perhaps there already is another way of achieving the situation described above with the existing controller? Many thanks!