This applies to environments Ryvn provisions. On an existing cluster, Ryvn does not
install its managed gateway, so ingress and TLS termination stay yours to run.
How it works
Ryvn uses Let’s Encrypt to issue and manage TLS certificates for both your custom domains andryvn.run subdomains.
When you deploy a public server:
- TLS certificates are automatically provisioned for all domains
- Certificates are renewed before they expire
- All HTTP requests are redirected to HTTPS
Internal endpoints
Internal servers get addresses on a separate internal domain, likeapi.internal.production.acme.ryvn.run, reachable only from your environment and connected networks. Ryvn provisions
and renews their certificates too, so they use HTTPS, and HTTP requests are redirected to HTTPS.
Environments with a .ryvn.internal domain serve internal endpoints over HTTP.