convez.ai
PluginDevOps & InfraestruturaIntermediário
txn2

kubefwd - Port Forwarding em Massa para Kubernetes

txn2/kubefwd

Acesse serviços Kubernetes localmente com nomes reais, sem conflitos de porta

Ver no GitHub
Muito bomPluginScore · de 0 a 100

Ferramenta que permite encaminhar em massa serviços Kubernetes para sua máquina local, atribuindo IPs únicos a cada serviço e eliminando conflitos de porta. Ideal para desenvolvimento local onde sua aplicação acessa serviços do cluster usando nomes de serviço, sem necessidade de configuração específica por ambiente.

Instalação

$npx convez-ai txn2/kubefwd

1 comando no terminal: detecta o formato do repositório (marketplace ou plugin avulso) e instala via Claude Code. Requer Node 18+ e o Claude Code instalado.

Métricas

Estrelas
4,2 mil
Forks
238
Acompanhando
29
Saúde
87%
Último commit
há 2 dias
Versão
v1.25.18
Issues abertas
7
Contribuidores
49

Casos de uso

  • Desenvolver localmente conectando a banco de dados, cache e APIs rodando no cluster
  • Testar integração entre microserviços sem Docker Compose ou configuração manual
  • Eliminar configurações específicas por ambiente usando strings de conexão idênticas

Veredito

Ferramenta madura e bem mantida (badges CNCF, OpenSSF, SLSA 3) que resolve um problema real de DevOps: desenvolvimento local integrado com clusters Kubernetes sem fricção de configuração. Essencial para times que usam K8s em staging/prod e querem paridade local.

README

A tradução para o português deste README ainda está na fila.

kubefwd (Kube Forward)

kubefwd - kubernetes bulk port forwarding

CNCF Landscape GitHub license codecov Go Report Card GitHub release GitHub Downloads OpenSSF Scorecard OpenSSF Best Practices SLSA 3

Documentation | Getting Started | User Guide | API Reference | MCP (AI Integration)

Develop Locally, Connect to Kubernetes

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.

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.

Bulk Kubernetes port forwarding with an interactive TUI, unique IPs per service, and automatic reconnection.

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.

kubefwd TUI - Main View

Quick Start

# Install (macOS)
brew install kubefwd

# Forward all services in a namespace with the interactive TUI
sudo -E kubefwd svc -n my-namespace --tui

Press ? for help, q to quit. See Getting Started for detailed installation and setup.

How It Works

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:

curl http://api-service:8080
mysql -h database -P 3306
redis-cli -h cache -p 6379

Features

  • Interactive TUI: Real-time service monitoring with traffic metrics
  • Unique IP per Service: Each service gets its own 127.x.x.x address
  • Auto-Reconnect: Reconnects when pods restart or connections drop
  • Bulk Forwarding: Forward all services in a namespace with one command
  • Live Traffic Monitoring: See bytes in/out and HTTP activity
  • Pod Log Streaming: View container logs in the TUI
  • REST API: Programmatic control via HTTP endpoints
  • MCP Support: Integration with AI assistants (Claude Code, Cursor)

Installation

macOS:

brew install kubefwd

Linux: Download .deb, .rpm, or .tar.gz from releases

Windows:

winget install txn2.kubefwd
# or
scoop install kubefwd

Docker:

docker run -it --rm --privileged \
  -v "$HOME/.kube:/root/.kube:ro" \
  txn2/kubefwd services -n my-namespace --tui

Usage

# Interactive mode (recommended)
sudo -E kubefwd svc -n default --tui

# Multiple namespaces
sudo -E kubefwd svc -n default,staging --tui

# Filter by label
sudo -E kubefwd svc -n default -l app=api --tui

# With REST API enabled
sudo -E kubefwd svc -n default --tui --api

Why kubefwd?

Unlike kubectl port-forward, kubefwd:

Featurekubectl port-forwardkubefwd
Services per commandOneAll in namespace
IP allocationlocalhost onlyUnique IP per service
Port conflictsManual managementNone (unique IPs)
Service name resolutionNot supportedAutomatic (/etc/hosts)
Auto-reconnectNoYes
Real-time monitoringNoTUI with metrics

See Comparison for detailed comparisons with Telepresence, mirrord, and other tools.

Documentation

Full documentation at kubefwd.com:

Requirements

  • kubectl configured with cluster access
  • Root/sudo access (for /etc/hosts and network interfaces)

Contributing

We welcome contributions for bug fixes, tests, and documentation. Feature development is limited to maintainers. See CONTRIBUTING.md.

License

Apache License 2.0


Open source by Craig Johnston, sponsored by Deasil Works, Inc.

Ver o original no GitHub

Bom para

Relacionados