Internal

DNS Setup

To access your applications using your domain name, configure a wildcard A DNS entry such as *.domain.com pointing to your Load Balancer IP. This ensures that any subdomain under domain.com resolves correctly to your services.

A full domain is required for KSaaS to work properly. This domain name has to be onboarded to your DNS provider. Make sure to also set the domainName value in your configuration for this matter.

Steps to Configure DNS for Metal3

1. Retrieve the Load Balancer IP from your Metal3 configuration file.

2. Create an A record in your DNS provider (e.g., AWS Route53, Cloudflare, or another provider):

   • Set the record type to A
   • Use *.domain.com as the hostname
   • Point it to the Load Balancer IP retrieved earlier

3. Verify the DNS resolution:

   nslookup app.domain.com

   Ensure it resolves to the Load Balancer IP.

Considerations

• The DNS entry should be configured before cluster generation to avoid disruptions.
• If using a dynamic Load Balancer IP, consider automating DNS updates using tools like external-dns.
• Ensure firewall and security group rules allow traffic to the Load Balancer IP.

By following these steps, your Metal3 cluster will be properly configured for DNS resolution, enabling seamless access to deployed applications.