Application networking has three distinct uses: communication inside a group, direct access through published ports, and HTTP/HTTPS access through Pingress.
Choose an entry point
| Need | Configuration |
|---|---|
| One application calls another | Same-group name and container port |
| Direct TCP or UDP access | Published port mapping |
| HTTP application with a domain | Pingress domain route to the container port |
| Encrypted browser access | Domain route plus a valid certificate |
Publishing a port is not required just to route a domain to an application. The route targets the container port, not the public port number.
Find a task
Application connectivity and published ports
Connect applications by name and expose container ports without confusing internal and public addresses.
Domains and routing
Route HTTP requests by domain, path prefix, headers, and cookies to an application port.
Automatic certificates and renewal
Prepare DNS and HTTP validation, enable ACME, and diagnose certificate issuance and renewal.
Custom certificates
Upload a matching certificate chain and private key, validate HTTPS, and manage renewal yourself.
Networking FAQ
Troubleshoot IPv6, client addresses, DNS, routing, and certificates.
Troubleshooting
Verify DNS, TCP reachability, TLS, routing, and the application response separately. A working console or an issued certificate does not prove every stage of the application request succeeds.