Kubefwd — Bulk Port Forwarding for Kubernetes Services

What it is

Kubefwd is a command-line tool that bulk-forwards Kubernetes services to your local machine and maps their DNS names to localhost. Instead of running kubectl port-forward for each service individually, kubefwd forwards all services in a namespace with a single command. Your local /etc/hosts is updated so you can access services by their Kubernetes DNS names as if they were running locally.

Kubefwd targets developers who work with multiple microservices on a remote Kubernetes cluster and want to run their local code against those services without modifying connection strings.

How it saves time or tokens

Manually port-forwarding each service requires multiple terminal tabs and remembering which local port maps to which service. Kubefwd eliminates this by forwarding all services in a namespace at once and mapping their names to localhost. Your application config uses the same service names in development and production, reducing environment-specific bugs.

How to use

1. Install kubefwd:

brew install txn2/tap/kubefwd

1. Forward all services in a namespace:

sudo kubefwd svc -n my-namespace

1. Access services by their Kubernetes names:

curl http://my-api:8080/health
curl http://my-database:5432

The sudo is required because kubefwd modifies /etc/hosts to add DNS entries.

Example

Forwarding specific services with label selectors:

# Forward only services with a specific label
sudo kubefwd svc -n dev -l app=backend

# Forward services from multiple namespaces
sudo kubefwd svc -n frontend -n backend

# Use a specific kubeconfig context
sudo kubefwd svc -n dev --context=staging-cluster

Once running, your application connects to http://user-service:3000 and the traffic routes to the pod in the cluster.

Related on TokRepo

• AI Tools for DevOps — Kubernetes development and operations tools
• Automation Tools — developer workflow automation

Common pitfalls

• Kubefwd requires root/sudo because it modifies /etc/hosts; on corporate machines with restricted permissions, this may be blocked
• Services with the same name in different namespaces will conflict in /etc/hosts; use one namespace at a time or label selectors to avoid collisions
• Kubefwd forwards to pods, not through Kubernetes service load balancing; if you need to test load balancing behavior, use the cluster directly