Writing that reply made me realize my error. I'm telling my LoadBalancer to
listen to 80/443 and route to 8090, but nginx-ingress listens on 80/443. The
service that nginx-ingress passes the request to is where port 8090 gets mapped.
Sorry for all that :( I'm still learning!
--
You received
Correct, that is the Cluster IP of my LoadBalancer service.
My Pods are listening on port 8090. I tried to curl port 80 because I figured
the LoadBalancer listens on 80 and 443 and directs the request to my
nginx-ingress.
But I also tried to curl port 8090 from inside a node: "curl
I am assuming 10.59.246.49 is your cluster IP? and port 80 is the
service port as defined in the Service.spec.ports[] ?
Are your pods actually listening on port 80? Or are they on a different port?
On Wed, Nov 8, 2017 at 9:41 AM, bg303 wrote:
> Thanks, Tim. That guide
Thanks, Tim. That guide was very informative. I was able to get through a few
of these steps:
Does the Service have any Endpoints? Yes - verified that three pods were
returned
Are the Pods working? Verified all three pods are working.
Is the kube-proxy working? Yes
Is kube-proxy writing
https://kubernetes.io/docs/tasks/debug-application-cluster/debug-service/
Does the Service have Endpoints?
On Tue, Nov 7, 2017 at 1:10 PM, bg303 wrote:
> I created a Deployment, Service, Ingress and then an nginx-ingress
> deployment. If I point my DNS record at any of
I created a Deployment, Service, Ingress and then an nginx-ingress deployment.
If I point my DNS record at any of the nodes running the nginx-ingress, I am
able to access to the service.
I then created a Service with spec.Type = LoadBalancer, pointed it to my
nginx-ingress, and pointed my DNS