Topic 1 Question 149

Associate Cloud Engineer

Topic 1 Question 149
You are running multiple VPC-native Google Kubernetes Engine clusters in the same subnet. The IPs available for the nodes are exhausted, and you want to ensure that the clusters can grow in nodes when needed. What should you do?
- Create a new subnet in the same region as the subnet being used.
- Add an alias IP range to the subnet used by the GKE clusters.
- Create a new VPC, and set up VPC peering with the existing VPC.
- Expand the CIDR range of the relevant subnet for the cluster.
ユーザの投票
コメント(12)
- Correct Answer is (D):
  
  gcloud compute networks subnets expand-ip-range NAME gcloud compute networks subnets expand-ip-range - expand the IP range of a Compute Engine subnetwork
  
  https://cloud.google.com/sdk/gcloud/reference/compute/networks/subnets/expand-ip-range
  
  👍 26
  ESP_SAP2020/08/21
- D: is the answer
  
  👍 12
  MohammedGhouse2020/08/12
- This might help
  
  Node limiting ranges The maximum number of Pods and Services for a given GKE cluster is limited by the size of the cluster's secondary ranges. The maximum number of nodes in the cluster is limited by the size of the cluster's subnet's primary IP address range and the cluster's Pod address range.
  
  The Cloud Console shows error messages like the following to indicate that either the subnet's primary IP address range or the cluster's Pod IP address range (the subnet's secondary IP address range for Pods) has been exhausted:
  
  Instance [node name] creation failed: IP space of [cluster subnet] is exhausted Note: Secondary subnets are not visible in Cloud Console. If you can't find the [cluster subnet] reported by the above error message it means that the error is caused by IP exhaustion in a secondary subnet. In this case check the secondary ranges of the primary subnet.
  
  https://cloud.google.com/kubernetes-engine/docs/concepts/alias-ips#node_limiters
  
  👍 6
  GCP_Student12021/02/28
シャッフルモード

ユーザの投票

コメント(12)