Launch docker not exposing ports to node

[radomirpolach]

When I launch docker image and setup ports, I cannot access the application on the ports specified, it only works when I assign dedicated IP address to a pod.

I can't even access the application on the local IP:

Code:

$ sudo k3s kubectl get services -n ix-alpha

NAME              TYPE       CLUSTER-IP      EXTERNAL-IP   PORT(S)         AGE

alpha-ix-chart   NodePort   172.17.213.61   <none>        9093:9093/TCP   36s

$ curl http://172.17.213.61:9093

curl: (7) Failed to connect to 172.17.213.61 port 9093: No route to host

 

[radomirpolach]

The issue seems to be related to the fact that I can't internally access apps running in dockers.

When I expose the app above to for example 10.0.0.100, I can access it as 10.0.0.100:9093, but I can't do that from within the TrueNAS.

Code:

$ curl http://10.0.0.100:9093

curl: (7) Failed to connect to 10.0.0.100 port 9093: No route to host

 

[radomirpolach]

Ok, for this to work, you need to "Provide access to node network" and disable rolling update.

 

[-jim]

Ok, for this to work, you need to "Provide access to node network" and disable rolling update.

How and where is that done?

 

[sretalla]

How and where is that done?

In a previous version of the official charts there was an option to adjust the container update policy (rolling update was one of the options)... no longer available a year later, so forget that bit.

For the other part, I assume you can see the checkbox labeled as indicated in the post above when creating a new app configuration.