$git clone https://github.com/txn2/kubefwd[Documentation](https://kubefwd.com) | [Getting Started](https://kubefwd.com/getting-started/) | [User Guide](https://kubefwd.com/user-guide/) | [API Reference](https://kubefwd.com/api-reference/) | [MCP (AI Integration)](https://kubefwd.com/mcp-integration/)
| 1 | # kubefwd (Kube Forward) |
| 2 | |
| 3 |  |
| 4 | |
| 5 | [](https://landscape.cncf.io/?item=app-definition-and-development--application-definition-image-build--kubefwd) |
| 6 | [](https://github.com/txn2/kubefwd/blob/master/LICENSE) |
| 7 | [](https://codecov.io/gh/txn2/kubefwd) |
| 8 | [](https://goreportcard.com/report/github.com/txn2/kubefwd) |
| 9 | [](https://github.com/txn2/kubefwd/releases) |
| 10 | [](https://github.com/txn2/kubefwd/releases) |
| 11 | [](https://scorecard.dev/viewer/?uri=github.com/txn2/kubefwd) |
| 12 | [](https://www.bestpractices.dev/projects/11659) |
| 13 | [](https://slsa.dev) |
| 14 | |
| 15 | |
| 16 | **[Documentation](https://kubefwd.com)** | **[Getting Started](https://kubefwd.com/getting-started/)** | **[User Guide](https://kubefwd.com/user-guide/)** | **[API Reference](https://kubefwd.com/api-reference/)** | **[MCP (AI Integration)](https://kubefwd.com/mcp-integration/)** |
| 17 | |
| 18 | ## Develop Locally, Connect to Kubernetes |
| 19 | |
| 20 | **kubefwd** enables developers to work on their local machine while seamlessly accessing services running in a Kubernetes cluster. If you're building a new API that needs to connect to a database at `db:5432`, an auth service at `auth:443`, and a cache at `redis:6379`, all running in your development cluster, kubefwd makes them available locally by their service names, exactly as they would appear in-cluster. No environment-specific configuration, no local service setup, no Docker Compose files. Just run `kubefwd` and your application's existing connection strings work. |
| 21 | |
| 22 | This is the essential use case: **reduce or eliminate environment-specific connection setup and configurations** during local development. Your code uses `http://api-gateway:8080` in production? It works the same way on your laptop with kubefwd. |
| 23 | |
| 24 | > Bulk Kubernetes port forwarding with an interactive TUI, unique IPs per service, and automatic reconnection. |
| 25 | |
| 26 | **kubefwd** is a command-line utility that bulk port forwards Kubernetes services to your local workstation. Each service gets its own unique loopback IP (127.x.x.x), eliminating port conflicts and enabling realistic local development with cluster services accessible by name. |
| 27 | |
| 28 |  |
| 29 | |
| 30 | ## Quick Start |
| 31 | |
| 32 | ```bash |
| 33 | # Install (macOS) |
| 34 | brew install kubefwd |
| 35 | |
| 36 | # Forward all services in a namespace with the interactive TUI |
| 37 | sudo -E kubefwd svc -n my-namespace --tui |
| 38 | ``` |
| 39 | |
| 40 | Press `?` for help, `q` to quit. See [Getting Started](https://kubefwd.com/getting-started/) for detailed installation and setup. |
| 41 | |
| 42 | ## How It Works |
| 43 | |
| 44 | <div align="center"> |
| 45 | <img width="654" alt="kubefwd - Kubernetes Port Forward Diagram" src="https://mk.imti.co/images/content/kubefwd-net.png"> |
| 46 | </div> |
| 47 | |
| 48 | kubefwd discovers services in your namespace, assigns each a unique loopback IP, updates `/etc/hosts` with service names, and establishes port forwards through the Kubernetes API. Access services by name just like in-cluster: |
| 49 | |
| 50 | ```bash |
| 51 | curl http://api-service:8080 |
| 52 | mysql -h database -P 3306 |
| 53 | redis-cli -h cache -p 6379 |
| 54 | ``` |
| 55 | |
| 56 | ## Features |
| 57 | |
| 58 | - **Interactive TUI**: Real-time service monitoring with traffic metrics |
| 59 | - **Unique IP per Service**: Each service gets its own 127.x.x.x address |
| 60 | - **Auto-Reconnect**: Reconnects when pods restart or connections drop |
| 61 | - **Bulk Forwarding**: Forward all services in a namespace with one command |
| 62 | - **Live Traffic Monitori |