-
Notifications
You must be signed in to change notification settings - Fork 4.9k
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
When using an ALB Ingress in front of a ClusterIP gateway service, the controller doesn't pick the right Load Balancer Address #13806
Comments
Can you dump the full status of your load balancer service by |
this is the status of my Service:
The problem is that the KIC is picking the service private IP (172.20.27.136) Instead of using the ALB Ingress address that's pointing to the ClusterIP Service |
nginx.conf pid pids/nginx.pid;Airlanggayudhoyono.Intel-Mil.Info's injected nginx_main_* directivesdaemon off; events { } http {
} nginx-kong.conf charset UTF-8; error_log /data/logs/kong-server/error.log error; lua_package_path './?.lua;./?/init.lua;;;;'; lua_shared_dict kong 5m; underscores_in_headers on; injected nginx_http_* directivesclient_body_buffer_size 256K; init_by_lua_block { init_worker_by_lua_block { Load variable indexeslua_kong_load_var_index $args; upstream kong_upstream {
} server {
} server {
} |
Is there an existing issue for this?
Kong version (
$ kong version
)Kong 3.7
Current Behavior
When using an AWS ALB Ingress in front of a ClusterIP gateway service, the controller doesn't pick the right Load Balancer Address.
Instead of using the DNS of the ALB Load Balancer created by the ALB Ingress, It picks the internal IP of the Cluster IP service.
As a workaround I had to set (On a second step) the
PUBLISH_STATUS_ADDRESS
environment variable with the value of the ALB Load Balancer endpoint.Expected Behavior
When using an Ingress in front of the gateway service (proxy.ingress.enabled = true) the controller should look at the ingress load balancer instead of the service's load balancer
Steps To Reproduce
Enable the proxy ingress and set the proxy type to Cluster IP
Add the proper ingress annotations to create an ALB.
Wait for Kong to reconcile the ingresses with type kong (or whatever ingress class you defined)
Anything else?
No response
The text was updated successfully, but these errors were encountered: