Google Professional Cloud Network Engineer Question 567
Select 3Google Cloud PlatformYou are managing a GKE cluster for a production application that requires dynamic DNS record updates for services deployed within the cluster. To automate DNS record management using Cloud DNS, you decide to use the external-DNS operator. Which of the following steps are required to configure external-DNS with Cloud DNS for your GKE cluster?
- A
Grant the GKE node service account the 'roles/dns.admin' IAM role for the Cloud DNS zone
- B
Deploy the external-DNS operator to the GKE cluster using a Helm chart or Kubernetes manifests
- C
Configure a private DNS zone in Cloud DNS to manage the DNS records for the cluster
- D
Provide the external-DNS operator with access to the Kubernetes API by creating a Kubernetes ServiceAccount and ClusterRoleBinding
- E
Create and configure a Cloud Storage bucket to store DNS configuration files for external-DNS
Show answer and explanation
Correct answers: A, B, D
Explanation
To configure external-DNS with Cloud DNS for a GKE cluster, you need to ensure that the operator has the necessary IAM permissions to manage Cloud DNS, is deployed in the cluster, and has access to the Kubernetes API. This allows the operator to monitor Kubernetes resources and dynamically update DNS records in Cloud DNS zones. Configuring a private DNS zone or using Cloud Storage is not relevant for this setup unless specific application requirements dictate otherwise.
- A. Correct.
Correct: The external-DNS operator requires permissions to manage Cloud DNS records. Granting the GKE node service account the 'roles/dns.admin' role ensures it can update DNS records in the specified Cloud DNS zone.
- B. Correct.
Correct: Deploying the external-DNS operator is a required step to enable dynamic DNS record management. The operator runs as a pod in the GKE cluster and automates DNS record updates.
- C. Incorrect.
Incorrect: Configuring a private DNS zone is not required unless the application explicitly needs a private zone. By default, external-DNS can work with publicly accessible Cloud DNS zones.
- D. Correct.
Correct: The external-DNS operator needs access to the Kubernetes API to monitor services and endpoints within the cluster. This is achieved by setting up a Kubernetes ServiceAccount and ClusterRoleBinding.
- E. Incorrect.
Incorrect: Cloud Storage is not used in this context. The external-DNS operator directly interfaces with the Kubernetes API and Cloud DNS, and no additional storage is required.