rutvik-cybersecurist opened a new issue, #2288: URL: https://github.com/apache/apisix-ingress-controller/issues/2288
### Current Behavior After running the installation steps detailed in this guide: https://apisix.apache.org/docs/ingress-controller/deployments/aws/ I ran this helm command: `helm install apisix apisix/apisix \ --set gateway.type=LoadBalancer \ --set ingress-controller.enabled=true \ --create-namespace \ --namespace ingress-apisix \ --set ingress-controller.config.apisix.serviceNamespace=ingress-apisix \ --set ingress-controller.config.apisix.adminAPIVersion=$ADMIN_API_VERSION` The helm install created a svc of type `NodePort` ### Expected Behavior Expected the `apisix-gateway` svc created to be of type `LoadBalancer` ### Error Logs _No response_ ### Steps to Reproduce 1. Create a cluster in Amazon EKS 2. Install APISIX using the following helm command: `helm install apisix apisix/apisix \ --set gateway.type=LoadBalancer \ --set ingress-controller.enabled=true \ --create-namespace \ --namespace ingress-apisix \ --set ingress-controller.config.apisix.serviceNamespace=ingress-apisix \ --set ingress-controller.config.apisix.adminAPIVersion=$ADMIN_API_VERSION` 3. List services in the `ingress-apisix` namespace to see that `apisix-gateway` svc has type: `NodePort` even though we explicitly set `gateway.type=LoadBalancer` ### Environment - APISIX Ingress controller version (run `apisix-ingress-controller version --long`): `apache/apisix-ingress-controller:1.8.0 /usr/local/openresty//luajit/bin/luajit ./apisix/cli/apisix.lua version 3.9.1` - Kubernetes cluster version (run `kubectl version`): `Server Version: v1.29.6-eks-db838b0` - OS version if running APISIX Ingress controller in a bare-metal environment (run `uname -a`) `Amazon Linux 2, kernel: 5.10.214-202.855.amzn2.aarch64` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
