kubefwd
Bulk port forward Kubernetes services to localhost with unique IPs and an interactive TUI for seamless local development.
What is kubefwd?
kubefwd is a command-line utility that bulk forwards Kubernetes services to a local workstation, enabling developers to work locally while accessing cluster services by their in-cluster names. It assigns each service a unique loopback IP to avoid port conflicts and updates /etc/hosts for service name resolution, eliminating environment-specific configuration.
Kubernetes developers and engineers who need to run applications locally while connecting to services (like databases, APIs, or caches) running in a remote Kubernetes cluster, without modifying connection strings or managing complex local setups.
Developers choose kubefwd over alternatives like kubectl port-forward because it forwards all services in a namespace with a single command, provides unique IPs per service to avoid port conflicts, automatically reconnects on pod changes, and includes an interactive TUI for real-time monitoring and log streaming.
Overview
Bulk port forwarding Kubernetes services for local development.
Use Cases
Best For
- Developing microservices locally that need to connect to multiple cluster services (e.g., databases, APIs, caches) using their production service names.
- Eliminating port conflicts when forwarding multiple Kubernetes services that use the same port numbers locally.
- Reducing environment-specific configuration by making cluster services available locally exactly as they appear in production.
- Monitoring real-time traffic metrics and streaming pod logs during local development via an interactive TUI.
- Integrating with AI assistants (like Claude Code or Cursor) through MCP support for programmatic control.
- Bulk forwarding all services in a Kubernetes namespace with auto-reconnect capabilities when pods restart.
Not Ideal For
- Teams that only need to forward one or two services and find kubectl port-forward sufficient, avoiding the overhead of bulk operations.
- Environments where root or sudo access is prohibited, such as corporate laptops with locked-down permissions.
- Development setups that rely on local Docker Compose or other non-Kubernetes orchestration tools without a Kubernetes cluster dependency.
Pros & Cons
Pros
Forwards all services in a namespace with a single command, as shown in the quick start example, eliminating the need for multiple kubectl port-forward instances.
Assigns unique 127.x.x.x loopback addresses to each service, preventing port conflicts when services use identical ports, a key advantage over kubectl port-forward.
Features a TUI with real-time traffic metrics and pod log streaming, enhancing debugging capabilities during local development, as highlighted in the features section.
Updates /etc/hosts to resolve Kubernetes service names locally, ensuring applications use the same connection strings as in production without manual configuration.
Cons
Requires sudo access to modify /etc/hosts and network interfaces, which is explicitly stated in the requirements and can be a barrier in secure or shared environments.
Automatically edits /etc/hosts, which might clash with other tools or require manual cleanup, leading to potential conflicts and maintenance overhead.
Designed only for forwarding to local loopback addresses, so it doesn't support scenarios requiring remote access or integration with service meshes like Istio.
Frequently Asked Questions
Related Projects
KubernetesProduction-Grade Container Scheduling and Management
MobyThe Moby Project - a collaborative project for the container ecosystem to assemble container-based systems
traefikThe Cloud Native Application Proxy
GiteaGit with a cup of tea! Painless self-hosted all-in-one software development service, including Git hosting, code review, team collaboration, package registry and CI/CD
Found a gem we're missing?
Open-Awesome is built by the community, for the community. Submit a project, suggest an awesome list, or help improve the catalog on GitHub.