txn2/kubefwd

Bulk port forwarding Kubernetes services for local development.

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 hour ago
Added to GitGenius on September 16th, 2026
Created on August 5th, 2018
Open Issues & Pull Requests: 10 (+0)
GitHub issues: Enabled
Number of forks: 236
Total Stargazers: 4,170 (+0)
Total Subscribers: 30 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 6.2 days
Mean response time: 270.5 days
90th percentile: 1032.1 days
Tracked items: 46

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 0
New in 7 days: 0
Closed in 7 days: 1
Avg open age: N/A days
Stale 30+ days: 0
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 1
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • enhancement (11)
  • bug (5)
  • help wanted (2)
  • question (2)
  • good first issue (1)

Detailed Description

kubefwd is a port-forwarding tool for Kubernetes that enables bulk forwarding of services to localhost for local development.

The tool solves the friction of developing against Kubernetes services by automating what would otherwise require manual port-forward commands for each service. Rather than running kubectl port-forward individually for multiple services, kubefwd discovers services in a namespace and establishes all forwarding rules at once, making them available on localhost. This approach eliminates repetitive setup and keeps local development workflows aligned with the actual services running in a cluster.

Developers working locally against Kubernetes-based backends should consider kubefwd when they regularly interact with multiple services in a namespace. It suits projects where the development environment mirrors production services and where developers need quick, repeatable access to those services without managing individual forwarding commands. The tool is particularly valuable in teams using Kubernetes for staging or development clusters where local testing against real services is part of the workflow.

The project shows consistent maintenance with regular updates addressing bugs and adding capabilities. Development activity includes responsiveness to issues and pull requests, indicating active engagement with users. The codebase receives improvements to core forwarding logic and namespace handling. The project maintains documentation and examples that reflect current usage patterns. There is ongoing work to expand integration points, including support for Claude MCP servers, suggesting the maintainers are adapting the tool to fit into broader development ecosystems.