Kubernetes
Port Forward & DNS
Forward Pod, Service, or Deployment ports and configure Dockerman's local DNS helper.
Forward a port from a Pod, Service, or Deployment to the local machine. Active forwards can reconnect automatically according to the Kubernetes settings.
Start a forward
- Open a supported resource and choose Port forward.
- Select the remote port and a free local port.
- Start the forward and use the displayed local address.
- Stop the forward from the active forwards list when finished.
Automatic DNS
When a forward starts, Dockerman registers a local name in the form <target>.<namespace>.<suffix>. The default suffix is k8s.local, and the built-in UDP DNS listener defaults to port 5353.
There is no separate DNS enable switch and Dockerman does not edit /etc/hosts.
Platform resolver setup
- macOS: configure an
/etc/resolver/<suffix>file that points to the Dockerman DNS port. - Linux: configure systemd-resolved or another resolver to send the selected suffix to the local DNS listener.
- Windows: automatic system resolver integration is not currently implemented.
Changing the suffix or port affects future registrations. Existing applications may cache DNS responses.