-
Notifications
You must be signed in to change notification settings - Fork 1.5k
LB configuraion is not working Using Gateway API #4175
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
Comments
Hi. Very exciting that you're trying out the Gateway implementation already! The current implementation is very basic, and doesn't support encrypted traffic (HTTPS) yet. Further, the TargetGroupConfiguration object is not yet supported. We wanted to get something out to give people a chance to feel out the implementation. I can see two issues:
|
@anannaya So excited that you are trying out Gateway API. to add to Zac's points, We only materialize the listeners for gateway if we find the associated routes for it and create tgs for the backends in those route to avoid creating leaking Target groups for the services which are not yet referred by any gateways. |
@shraddhabang @zac-nixon Thanks a lot for responding . I would like replicate the same ingress resources using the Gateway-api
|
Migrating the k8s Ingress to Gateway API with a the istio ingress pods . Here is my config .
I see ALB got created but No target groups or listeners.
aws-loadbalancer-controller-gateway aws-loadbalancer-controller k8s-istiosys-awsloadb-dfdfdfdfd-1125923642.us-east-1.elb.amazonaws.com Unknown 4h19m
The text was updated successfully, but these errors were encountered: