It does not work with NodePort configuration (localhost:3000 is hardcoded) about spekt8 HOT 5 CLOSED

You can use ssh tunneling as a workaround.

My example k8s environment is 3 nodes built with vagrant. I create ssh tunnel using command:

ssh -i ~/vagrant/k8s/.vagrant/machines/node1-master/virtualbox/private_key -L 127.0.0.1:3000:192.168.33.11:30002 [email protected]

Then spekt8 page can be accessed from local host with http://localhost:3000

from spekt8.

You can use ssh tunneling as a workaround.

My example k8s environment is 3 nodes built with vagrant. I create ssh tunnel using command:

ssh -i ~/vagrant/k8s/.vagrant/machines/node1-master/virtualbox/private_key -L 127.0.0.1:3000:192.168.33.11:30002 [email protected]

Then spekt8 page can be accessed from local host with http://localhost:3000

this worked for me but just shouldn't be necessary. Please allow remote access instead of hardcoding localhost:3000

from spekt8.

Yep, same problem for me.

localhost:3000 is hardcoded, for example in

and

and

from spekt8.

Same problem here.

from spekt8.

I have a really dirty workaround. I entered the container on the node running the pod with

sudo docker exec -it <PODID> bash

and then installed a text editor

apt-get update && apt-get install nano

then I edited the main.js file at /usr/src/app/dist and replaced all occurences of "localhost:3000" with the actual IP under which I made the webinterface accessiable

(FYI: kubectl port-forward --address 0.0.0.0 deployment/spekt8 3000:3000 if thats interesting for anyone. I could then just connect to <KUBERNETESMASTER_IP>:3000 on my workstation).

Then the webinterface worked on a reload. refresh button did not work, but I could reload again.

from spekt8.