You can add custom domains to your Ryvn installations. The configuration method depends on your service type:

  • Server Services: Use the Ryvn dashboard for domain management
  • Helm Chart Services: Configure domains directly in your chart’s ingress values

​
Server Services

Server services can add custom domains through the Ryvn dashboard. Custom domains are proxied through Ryvn’s infrastructure, which handles TLS certificate provisioning and traffic routing automatically.

​
Adding a Custom Domain

1

Enable Public Networking

  1. Navigate to your installation in the Ryvn dashboard
  2. Go to the installation’s Settings page
  3. Click on the Networking tab
  4. Switch to Public networking mode
  5. Wait about 10 seconds for your installation to connect to the external load balancer
2

Add Custom Domain

  1. In the custom domain field, enter your domain name
  2. Click Save

For domains with Unicode characters, convert to Punycode first (e.g., ëxample.com becomes xn--xample-ova.com). You can use tools like Punycoder for the conversion.

3

Configure DNS

  1. Note the external load balancer hostname or IP address displayed in the UI below the custom domain field
  2. Log in to your domain provider (like Cloudflare, Namecheap, or GoDaddy)
  3. Navigate to DNS settings
  4. Create a DNS record:
TypeNameValue
CNAME@ or subdomainLoad balancer hostname/IP from step 1

Some DNS providers call this record type ALIAS or ANAME instead of CNAME. They serve the same purpose.

4

Connect and Verify

  1. Head back to Ryvn and click Connect
  2. Ryvn will verify domain ownership and create a TLS certificate
  3. Once complete, verify your domain is accessible over HTTPS

​
Helm Chart Services

Helm charts on Ryvn can be configured with custom domains through ingress configuration. Unlike server services which use the dashboard for domain management, helm charts require direct configuration in your chart’s values.

​
Ryvn Networking

Ryvn environments come pre-configured with the following components for custom domain management:

  1. Ingress Controllers: Pre-configured NGINX ingress controllers:

    • external-nginx for public-facing services
    • internal-nginx for VPC-internal services

  2. Certificate Management: Automatic TLS certificates via cert-manager with:

    • external-issuer for public domains
    • internal-issuer for internal domains

  3. DNS Management: External DNS automatically manages DNS records for ryvn.run domains and internal domains

​
Adding a Custom Domain

1

Ensure Ingress Template

Make sure your helm chart has an ingress.yaml template in the templates/ directory.

See the Kubernetes Ingress documentation for template examples and configuration details.

2

Configure Ingress Values

Update your ingress configuration through the Ryvn dashboard:

  1. Go to your installation’s Settings in the Ryvn dashboard
  2. Navigate to Helm Values
  3. Add or update the ingress section:
ingress:
  enabled: true
  className: external-nginx  # Use external-nginx for public domains
  annotations:
    cert-manager.io/cluster-issuer: external-issuer
  hosts:
    - host: myapp.example.com
      paths:
        - path: /
          pathType: Prefix
  tls:
    - secretName: myapp-tls
      hosts:
        - myapp.example.com
  1. Click Save to deploy the changes

For internal-only services, use className: internal-nginx and cert-manager.io/cluster-issuer: internal-issuer

3

Configure DNS Records

Point your domain to the appropriate load balancer:

  1. Get the load balancer hostname:

    • Go to your installation’s Resources tab in the Ryvn dashboard
    • Find your ingress resource
    • Copy the load balancer hostname/address

  2. Create DNS records with your domain provider:

TypeNameValue
CNAME@ or subdomainLoad balancer hostname from step 1

For apex domains (example.com), use ALIAS or ANAME record types if supported by your DNS provider, otherwise use A records with the load balancer IPs.

4

Verify

Once DNS propagates, your application will be accessible at your custom domain with automatic HTTPS certificates.

​
Using ryvn.run Domains

Ryvn provides template variables for automatic ryvn.run domain generation:

ingress:
  enabled: true
  className: external-nginx
  annotations:
    cert-manager.io/cluster-issuer: external-issuer
  hosts:
    - host: myapp.{{ .ryvn.env.state.public_domain.name }}
      paths:
        - path: /
          pathType: Prefix
  tls:
    - secretName: myapp-tls
      hosts:
        - myapp.{{ .ryvn.env.state.public_domain.name }}

This automatically resolves to your environment’s configured public domain.

​
Troubleshooting

Common DNS issues and solutions:

Verify DNS propagation:

nslookup myapp.example.com
dig myapp.example.com

Check if DNS records are correct:

dig myapp.example.com CNAME
dig myapp.example.com A

Test from different locations:

# Test with different DNS servers
nslookup myapp.example.com 8.8.8.8
nslookup myapp.example.com 1.1.1.1

Common solutions:

  • Wait for DNS propagation (can take up to 48 hours)
  • Verify DNS records are correctly configured with your domain provider
  • Clear local DNS cache: sudo dscacheutil -flushcache (macOS) or ipconfig /flushdns (Windows)

​
Advanced Configuration

​
Custom Annotations

Add custom nginx annotations for advanced routing:

ingress:
  enabled: true
  className: external-nginx
  annotations:
    cert-manager.io/cluster-issuer: external-issuer
    nginx.ingress.kubernetes.io/rewrite-target: /
    nginx.ingress.kubernetes.io/ssl-redirect: "true"
    nginx.ingress.kubernetes.io/force-ssl-redirect: "true"