Use `kix pf`

Use kix pf to reach a package workload from your machine without first looking up its Kubernetes resource name.

Forward a local port

Provide the cluster, package instance, and a LOCAL:REMOTE port mapping:

Run in kix-examples/

❱ kix pf how-to-application production 8080:80

While the command is running, open another terminal and connect through the local port:

❱ curl http://127.0.0.1:8080

Kix resolves production to its primary workload, then keeps the port-forward attached to that workload. Stop it with Ctrl-C.

Let kubectl choose the local port

Prefix the remote port with a colon and leave the local side empty:

Run in kix-examples/

❱ kix pf how-to-application production :80

kubectl prints the selected local port when the forward is ready.

Do not use a bare 80 for this. Kix passes port specifications directly to kubectl port-forward, which interprets a single number as both the local and remote port. A bare 80 therefore means 80:80 and may fail because local port 80 is occupied or requires additional privileges.

Forward more than one port

Add each mapping as another argument:

Run in kix-examples/

❱ kix pf my-cluster application 8080:80 8443:443

Choose the listening address

The forwarded port listens on localhost by default. Use --address when it must listen on another local interface:

Run in kix-examples/

❱ kix pf how-to-application production 8080:80 --address 0.0.0.0

Binding to 0.0.0.0 makes the port reachable through every network interface on your machine. Only do this on a trusted network and when the service is safe to expose.

If an instance name is ambiguous, qualify it as <namespace>/<name>. Pass --context to select a Kubernetes context and --flake to evaluate the cluster from another directory.

See the pf command reference for every option.