---------------------- If you're having issues with the Garden-installed nginx ingress controller not exposing ports, there are a few things to check. When Garden installs the nginx ingress controller, it should create a service that exposes ports for HTTP (typically port 80) and HTTPS. If you can't connect to your services through the ingress, here are some troubleshooting steps: 1. **Check the external IP of the ingress controller**: Run the following command to see if the ingress controller has an external IP:

kubectl get svc -n garden-system

Look for the

garden-nginx-nginx-ingress-controller

service and check its EXTERNAL-IP. If it's pending or doesn't have an external IP, that could be the issue. 2. **Update DNS records if needed**: If you've recently reinstalled the Garden system services, the ingress controller might have been assigned a new IP address. As mentioned in the [troubleshooting documentation](), you may need to update your DNS records with the new IP. 3. **Check ingress configuration**: Make sure your services have proper ingress configurations. Each service should have an

ingresses

section that specifies the path and port, like:

ingresses:
     - path: /my-service
       port: http

The

port

should match a named port in your service configuration, as shown in the [Your First Project tutorial]().

4. **Verify ingress HTTP port**: By default, Garden uses port 80 for HTTP ingress. You can configure this with the

ingressHttpPort

setting in your kubernetes provider configuration if needed, as described in the [kubernetes provider documentation](). If you're using a remote Kubernetes cluster, you might need additional setup for ingress, TLS, and DNS as outlined in the [Remote K8s tutorial](). If you're still having issues, please provide more details about your environment (local or remote cluster) and your Garden configuration. ---------------------- Note: you can ask me a follow up question by @ mentioning me again :speech_balloon: ----------------------

message has been deleted