It does not work with NodePort configuration (localhost:3000 is hardcoded)

Because of network and firewall and other reasons, I can’t just do kubectl port-forward deployment/spekt8 3000:3000

Instead I had to install it using NodePort.

Now spekt8 shows me a blank screen for it tries to access localhost:3000 instead of THE_IP_ADDRESS:THE_PORT (i.e. this localhost:3000 is harcoded)

below are the YAML settings I used to install it:

---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: spekt8
spec:
  selector:
    matchLabels:
      k8s-app: spekt8
  replicas: 1
  template:
    metadata:
      labels:
        k8s-app: spekt8
    spec:
      containers:
        - name: spekt8
          image: elliotxkim/spekt8
          ports:
            - containerPort: 3000

---
kind: Service
apiVersion: v1
metadata:
  name: spekt8
  labels:
    k8s-app: spekt8
spec:
  ports:
  - protocol: TCP
    port: 3000
  type: NodePort
  selector:
    k8s-app: spekt8

[cvernooy23]

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 vagrant@192.168.33.11

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

[mari6274]

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 vagrant@192.168.33.11

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