Using Kops loadbalancer to access services installed on the cluster

[ankur6ue]

Hello, I'm attempting to access web services running on the cluster through the network load balancer created by Kops, through which kubctl accesses the kubernetes API server.

I first created a nginx pod on the cluster and verified and exposed it via nodeport service and then via loadbalancer. I verified I can access it from my desktop using both.

Now I'm trying to access the nginx pod through the kops created loadbalancer. To do this, I created a target group as shown below

I pointed that targetgroup to a port on the controlplane instance, where a nodeport service is listening

I can access the nginx server via the nodeport service by typing instance ip address:nodeport service port number, but not via the network load balancer..

Any tips on how to set this up?

[baka126]

@ankur6ue I believe the nlb created by kops is only for touting traffic to master node for kube api access. For accessing workloads you would have to create a separate LB either through service type Load Balancer or using ingress resources with annotation.
If you do not want to use NLB for kube api access you can use route53 dns configuration instead.

[ankur6ue]

Hello, it is indeed possible to use the NLB created by Kops to route traffic to a baremetal ingress.. I wrote a post about it:

https://github.com/ankur6ue/baremetal_ingress_from_nlb

There are several gotchas not covered anywhere.. particularly related to health checks.