Additional ports and paths

Use Additional ports and paths in an App's Settings tab to configure an additional container and ClusterIP Service port. This is an App-level setting: after you save and deploy the pending change, it affects every environment of that App.

Each mapping needs a port from 1 through 65535. The HTTP path is optional.

• A mapping such as port 3001 with no path makes port 3001 available only inside the cluster.
• A mapping such as port 3001 and path /api also exposes that port through the App's existing HTTP ingress hosts at /api. Quave ONE rewrites the request path for the target port.

For example, an App that serves a private metrics endpoint and a public API could use:

Port	HTTP path	Result
9090	(empty)	Cluster-internal metrics port
3001	/api	Available through the App's existing hosts at /api

The editor prevents duplicate ports and paths, and HTTP paths must begin with / (for example, /api). Remove every row and save to intentionally clear all additional mappings.

Scope and limitations

Additional ports and paths are supported for Direct and Connect Apps where the existing Extra Path capability is available. Functions and Jobs do not show this setting because they do not support it.

This does not create arbitrary public TCP exposure, independent Kubernetes Services, new hostnames, load balancers, or load-balancer rules. It uses the App's existing HTTP ingress hosts only when you configure an HTTP path. Use the normal deployment flow to apply the resulting pending changes.