Forwarding of headless service is not showing up

[ErlendFax]

When running kubefwd on our namespace it forwards all services except the headless one. It's found in the registry and started but does not show up. The name of the service is redpanda and the name name of the namespace is redpanda.

Shouldn't I be able to reach or ping redpanda after starting kubefwd?

All services:

k get svc -n redpanda 
NAME                                  TYPE        CLUSTER-IP      EXTERNAL-IP   PORT(S)                                                       AGE
console                               ClusterIP   10.62.254.157   <none>        8080/TCP                                                      168d
grafana                               ClusterIP   10.62.242.154   <none>        80/TCP                                                        167d
prometheus-kube-state-metrics         ClusterIP   10.62.251.134   <none>        8080/TCP                                                      5d16h
prometheus-prometheus-node-exporter   ClusterIP   10.62.253.112   <none>        9100/TCP                                                      5d16h
prometheus-prometheus-pushgateway     ClusterIP   10.62.253.203   <none>        9091/TCP                                                      5d16h
prometheus-server                     ClusterIP   10.62.252.17    <none>        80/TCP                                                        5d16h
redpanda                              ClusterIP   None            <none>        <none>                                                        11d
redpanda-external                     NodePort    10.62.247.9     <none>        9644:31644/TCP,9094:31092/TCP,8083:30082/TCP,8080:30081/TCP   11d

kubefwd started:

$ sudo kubefwd svc -n redpanda -v                          
...
INFO[10:03:53] Version 1.22.4                               
INFO[10:03:53] https://github.com/txn2/kubefwd              
INFO[10:03:53]                                              
INFO[10:03:53] Press [Ctrl-C] to stop forwarding.           
INFO[10:03:53] 'cat /etc/hosts' to see all host entries.    
INFO[10:03:53] Loaded hosts file /etc/hosts                 
INFO[10:03:53] HostFile management: Original hosts backup already exists at /Users/erlend/hosts.original 
INFO[10:03:54] Successfully connected context: gke_hark-tech_europe-west1-b_dev 
DEBU[10:03:54] Registry: Start forwarding service prometheus-server.redpanda.gke_hark-tech_europe-west1-b_dev 
DEBU[10:03:54] Registry: Start forwarding service prometheus-prometheus-pushgateway.redpanda.gke_hark-tech_europe-west1-b_dev 
DEBU[10:03:54] Registry: Start forwarding service prometheus-kube-state-metrics.redpanda.gke_hark-tech_europe-west1-b_dev 
DEBU[10:03:54] Registry: Start forwarding service console.redpanda.gke_hark-tech_europe-west1-b_dev 
DEBU[10:03:54] Registry: Start forwarding service redpanda-external.redpanda.gke_hark-tech_europe-west1-b_dev 
DEBU[10:03:54] Registry: Start forwarding service grafana.redpanda.gke_hark-tech_europe-west1-b_dev 
DEBU[10:03:54] Registry: Start forwarding service prometheus-prometheus-node-exporter.redpanda.gke_hark-tech_europe-west1-b_dev 
DEBU[10:03:54] Registry: Start forwarding service redpanda.redpanda.gke_hark-tech_europe-west1-b_dev 
DEBU[10:03:54] Resolving: prometheus-prometheus-node-exporter to 127.1.27.1 (prometheus-prometheus-node-exporter) 
INFO[10:03:54] Port-Forward:       127.1.27.1 prometheus-prometheus-node-exporter:9100 to pod prometheus-prometheus-node-exporter-7z57n:9100 
DEBU[10:03:54] Resolving: prometheus-prometheus-pushgateway to 127.1.27.2 (prometheus-prometheus-pushgateway) 
INFO[10:03:54] Port-Forward:       127.1.27.2 prometheus-prometheus-pushgateway:9091 to pod prometheus-prometheus-pushgateway-767ddfb9bd-5hsk8:9091 
DEBU[10:03:54] Resolving: prometheus-kube-state-metrics to 127.1.27.3 (prometheus-kube-state-metrics) 
INFO[10:03:54] Port-Forward:       127.1.27.3 prometheus-kube-state-metrics:8080 to pod prometheus-kube-state-metrics-84bb75bf7d-hmshk:8080 
DEBU[10:03:54] Resolving: prometheus-server to 127.1.27.8 (prometheus-server) 
INFO[10:03:54] Port-Forward:       127.1.27.8 prometheus-server:80 to pod prometheus-server-6df769864-tptk6:9090 
DEBU[10:03:54] Resolving: grafana to 127.1.27.9 (grafana)   
INFO[10:03:54] Port-Forward:       127.1.27.9 grafana:80 to pod grafana-5d694f59d6-6km67:3000 
DEBU[10:03:54] Resolving: console to 127.1.27.10 (console)  
INFO[10:03:54] Port-Forward:      127.1.27.10 console:8080 to pod console-675b68844c-8fxhp:8080 
DEBU[10:03:54] Resolving: redpanda-external to 127.1.27.11 (redpanda-external) 
INFO[10:03:54] Port-Forward:      127.1.27.11 redpanda-external:9644 to pod redpanda-0:9644 
DEBU[10:03:54] Resolving: redpanda-external to 127.1.27.11 (redpanda-external) 
INFO[10:03:54] Port-Forward:      127.1.27.11 redpanda-external:9094 to pod redpanda-0:9094 
DEBU[10:03:54] Resolving: redpanda-external to 127.1.27.11 (redpanda-external) 
INFO[10:03:54] Port-Forward:      127.1.27.11 redpanda-external:8083 to pod redpanda-0:8083 
DEBU[10:03:54] Resolving: redpanda-external to 127.1.27.11 (redpanda-external) 
INFO[10:03:54] Port-Forward:      127.1.27.11 redpanda-external:8080 to pod redpanda-0:8080 
I0213 10:03:55.556171    8526 request.go:665] Waited for 1.115214374s due to client-side throttling, not priority and fairness, request: GET:https://35.240.73.146/api/v1/namespaces/redpanda/pods/redpanda-0

[ErlendFax]

When stopping kubefwd I noticed this:

DEBU[10:25:09] Registry: Stopping service redpanda.redpanda.gke_hark-tech_europe-west1-b_dev with 0 port-forward(s) 

So it seems it doesn't work since there are no ports to forward so that makes sense I guess.

Is there any way I can get this working? I'm kinda new to this but I know other pods can reach redpanda on redpanda.redpanda:9093 ... so was hoping I could reach it from my local machine using this tool.