Pingress routes requests to the application’s container port. Enable it on reachable servers before configuring application domains.
Configure in order
First make the application listen on the intended container interface and port. Verify its replicas and logs. For a domain, enable Pingress, point DNS to its reachable entry servers, and allow ports 80/443. Then configure the route and certificate.
An Operator can manage application routes; an Admin configures platform components. A platform management domain has its own settings.
Add a route
- Point the domain’s A/AAAA records to the entry servers.
- Confirm inbound ports 80/443 and the application’s listening port.
- Add a domain route in application settings.
- Enter a hostname such as
app.example.comand its target container port. HTTPS is selected by default; clear it to use HTTP. - Save and test a matching request.
Use a hostname, not a URL, IP address, wildcard, port, or path. Domain input is normalized to lowercase and requires multiple labels.
Match conditions
A route may additionally match a path prefix, request header, or cookie. Conditions on the same route are combined: the request must satisfy them all. A header or cookie can test presence or a specific value.
The prefix /api matches /api and /api/users, but not /apix. Matching does not remove or rewrite that prefix before forwarding.
More specific conditions and longer prefixes affect priority. Avoid ambiguous overlapping routes; do not rely on the order shown in the form as a precedence control.
Verify and troubleshoot
Test both a matching request and a request expected not to match. Inspect access logs for the domain, target, status, and timing.
A gateway error can mean the backend is unavailable even when DNS and TLS succeed. An unexpected application can indicate overlapping conditions or an incorrect target port.
HTTPS needs an automatic or custom certificate. Platform console domains are configured separately.