Custom DNS resolution fails for Kubernetes guest clusters created in VCF Automation
Article ID: 448390
Updated On:
Products
Issue/Introduction
When you deploy VMware Kubernetes Engine (VKS) guest clusters from VCF Automation, custom DNS resolution configured within the VPC Service Profile does not function.
The newly created Kubernetes guest clusters fail to resolve external or custom domain names using the expected VPC-configured DNS servers.
Environment
Software: VMware Cloud Foundation (VCF) 9.1
Component: VCF Automation / VKS Guest Clusters / VPC Service Profile
Cause
This issue occurs because newly created guest clusters inherit the DNS configuration of the Supervisor Infrastructure / Workload Network instead of utilizing the VPC-configured DNS servers.
In VCF 9.1, the DNS configuration within the VPC Service Profile is an unconsumed attribute for VKS guest clusters.
Resolution
As a workaround, configure your required DNS settings directly on the Supervisor Workload Network instead of the VPC Service Profile in Automation. Guest clusters will automatically inherit the correct DNS configuration from the Supervisor Workload Network upon creation.
The functionality of using VPC-configured DNS for Kubernetes clusters created in VCF Automation is currently on the VCF product roadmap.
Subscribe to this knowledge article to get updates on this issue.
Additional Information
Feedback
