Skip to main content

Domain Naming Conventions

Status​

Accepted

Context​

We need to maintain consistent domain naming across different Kubernetes clusters (AMD64 and ARM64) to avoid confusion and configuration errors.

Decision​

We will use different top-level domains for each cluster, with service-specific subdomains:

  1. AMD64 Cluster (95.217.130.127):

    • Domain: *.arcana.cfd
    • Services:
      • Mercury Bot: mercury-bot.arcana.cfd
      • Mercury TA: mercury-ta.arcana.cfd

  2. ARM64 Cluster (195.201.35.33):

    • Domain: *.arcana.monster
    • Services:
      • Mercury Bot: mercury-bot.arcana.monster
      • Mercury TA: mercury-ta.arcana.monster

Consequences​

Positive​

  • Clear separation between clusters
  • Service-specific subdomains for better organization
  • Easier troubleshooting
  • Reduced chance of misconfiguration
  • Simplified SSL certificate management

Negative​

  • Need to maintain two sets of DNS records
  • Additional SSL certificates required

Implementation Notes​

  1. DNS Configuration:

    • Configure A records for each service subdomain pointing to the respective cluster IP
    • Use cert-manager with Let's Encrypt for SSL certificates

  2. Kubernetes Configuration:

    • Use cluster-specific ingress configurations with service-specific subdomains
    • Maintain separate TLS secrets for each domain