I'm having difficulty accessing the NodePort service on my Kubernetes cluster.
purpose
configure the ALB Ingress controller so that I can use websockets and http / 2
configure the NodePort service as requested by this controller
Steps taken
Earlier on AWS eu-west-1, the Kops cluster was created (version 1.6.2). Added kops add-ons for nginx login as well as Kube-lego. ELB is working fine.
Install ALB Ingress Controller using custom AWS keys using the IAM profile specified in this project.
Service type changed from LoadBalancer to NodePort using kubectl replace -force
> kubectl describe svc my-nodeport-service
Name: my-node-port-service
Namespace: default
Labels: <none>
Selector: service=my-selector
Type: NodePort
IP: 100.71.211.249
Port: <unset> 80/TCP
NodePort: <unset> 30176/TCP
Endpoints: 100.96.2.11:3000
Session Affinity: None
Events: <none>
> kubectl describe pods my-nodeport-pod
Name: my-nodeport-pod
Node: <ip>.eu-west-1.compute.internal/<ip>
Labels: service=my-selector
Status: Running
IP: 100.96.2.11
Containers:
update-center:
Port: 3000/TCP
Ready: True
Restart Count: 0
(ssh into node)
$ sudo netstat -nap | grep 30176
tcp6 0 0 :::30176 :::* LISTEN 2093/kube-proxy
results
ALB curl hanging
curl from <public ip address of all nodes>:<node port for service>freezes
Expected
Curl ALB node: node-port 200 "Ok" ( http )
:
, github, , :