kubefwd 1.25.7 (new formula)

[cjimti]

kubefwd is a Kubernetes port-forwarding utility (originally developed in 2018) that forwards multiple services from one or more namespaces, adding /etc/hosts entries for local development. Unlike kubectl port-forward, each service gets its own unique loopback IP (127.x.x.x), allowing multiple services to use the same port simultaneously and their cluster hostnames.

Key features:

• Bulk port forwarding with automatic /etc/hosts management
• Unique loopback IPs per service (no port conflicts)
• Auto-reconnect on pod restarts
• Interactive TUI mode
• MCP mode for AI agent integration
• Shell completions (bash, zsh, fish, powershell)

Project stats:

• ~4,000 GitHub stars, 219 forks
• Active since 2018, featured in "essential Kubernetes developer tools" lists
• Apache-2.0 license

Previous submission: PR #45721 was submitted by a community member in 2019 and closed due to lack of follow-through. This submission is from the project maintainer and I will be responsive to feedback.

• Have you followed the guidelines for contributing?
• Have you ensured that your commits follow the commit style guide?
• Have you checked that there aren't other open pull requests for the same formula update/change?
• Have you built your formula locally with HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>, where <formula> is the name of the formula you're submitting?
• Is your test running fine brew test <formula>, where <formula> is the name of the formula you're submitting?
• Does your build pass brew audit --strict <formula> (after doing HOMEBREW_NO_INSTALL_FROM_API=1 brew install --build-from-source <formula>)? If this is a new formula, does it pass brew audit --new <formula>?

All items are checked because I verified them:

• Built from source (28 seconds)
• brew test passed
• brew audit --strict --new --online passed
• Commit format: kubefwd 1.25.7 (new formula)
• No other open PRs for kubefwd

[github-actions]

Thanks for contributing to Homebrew! 🎉 It looks like you're having trouble with a CI failure. See our contribution guide for help. You may be most interested in the section on dealing with CI failures. You can find the CI logs in the Checks tab of your pull request.