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?
A.
Create a new subnet in the same region as the subnet being used.
B.
Add an alias IP range to the subnet used by the GKE clusters.
C.
Create a new VPC, and set up VPC peering with the existing VPC.
D.
Expand the CIDR range of the relevant subnet for the cluster.
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
Ok D it is, here's the GKE specific documentation
https://cloud.google.com/kubernetes-engine/docs/concepts/alias-ips
Every subnet must have a primary IP address range. You can expand the primary IP address range at any time, even when Google Cloud resources use the subnet; however, you cannot shrink or change a subnet's primary IP address scheme after the subnet has been created. The first two and last two IP addresses of a primary IP address range are reserved by Google Cloud.
D. Expand the CIDR range of the relevant subnet for the cluster.
Expanding the CIDR range of the relevant subnet for the cluster would increase the number of available IP addresses and allow the clusters to grow when needed. This can be done by modifying the existing subnet's IP address range in the VPC network settings. Adding a new subnet or VPC peering would not directly address the issue of running out of available IP addresses in the current subnet. Adding an alias IP range to the subnet could provide additional IP addresses, but may not be sufficient for long-term growth.
Please provide the reason why you choose C as the right answer. ESP_SAP explains clearly about the reason why he choose D as the right answer even he add Google Documentation link too to prove his answer.
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
UHmmm, 1 question. The description of the problem says that the ip's are EXHAUSTED. So, no more IP's available in this subnet.
It also states that we're having a multi-VPC environment... as allways we should not interpret, just take the questions literally.
IF we do not know the actual size of the deployment it cna be ANY size, adn if IP's are EXHAUSTED, it should BE, BIG as Galactic sized or so....
With all this I wonder if the right answer it is not C...
D. Expand the CIDR range of the relevant subnet for the cluster.
upvoted 1 times
...
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
ESP_SAP
Highly Voted 3 years, 6 months agomagistrum
3 years, 2 months agoMohammedGhouse
Highly Voted 3 years, 6 months agoSSPC
3 years, 6 months agoCaptain1212
Most Recent 6 months agoBobbybash
1 year agoAwesomeGCP
1 year, 4 months agolearn_GCP
1 year, 5 months agosonuricky
1 year, 7 months agoryumada
1 year, 7 months agoBumbah
1 year, 8 months agoAzureDP900
1 year, 8 months agoGCP_Student1
3 years agoGCP_Student1
2 years, 11 months agoOzymandiax
3 years, 2 months agoakshaym87
2 years, 1 month agoBhagirathi
3 years, 3 months agohicham
3 years agoswatititame
3 years, 3 months ago