GoogleCloudPlatform / GoogleCloudPlatform/gsutil
Unable to create a GKE pool with reserved multiple local SSDs
- Dominant language
- Python
- Stars
- 918
- Forks
- 335
- PR merge metrics
- No merged PRs in 30d
Description
Hello,
I am trying to create and use reservation of local SSD and VM, but the unclear error is returned. Here are easy steps to reproduce:
1. Create a reservation with two local SSDs and `n2-standard-2` VM.
`gcloud compute reservations create reservation --machine-type=n2-standard-2 --zone="us-central1-c" --vm-count=1 --require-specific-reservation --local-ssd=size=375,interface=scsi --local-ssd=size=375,interface=scsi`
Log: `Created [https://www.googleapis.com/compute/v1/projects/{{PROJECT WAS HERE}}/zones/us-central1-c/reservations/reservation].`
2. Trying to create a GKE pool by using reserved resources
`gcloud container node-pools create np --cluster data --zone="us-central1-c" --machine-type=n2-standard-2 --reservation-affinity specific --reservation=reservation --num-nodes 1 --local-ssd-count=2`
Log: `ERROR: (gcloud.container.node-pools.create) ResponseError: code=429, message=Reservation does not have enough resources for the request: specific reservation "reservation" is insufficient for node pool "np4" at zone "us-central1-c": required 1 and short of 1 VM count of machine type n2-standard-2.`
I tried a lot of different ways to do it, but nothing helped. I suppose the problem reproduces when requested more than 1 local SSD.
I created this issue in `gsutil` project since the only way to create a GKE pool with reserved resources is `gcloud` tool (or directly API)
Contributor guide
Research direction
No repository files or tests are identified. Start by reproducing the reservation and GKE node-pool commands in the issue, then investigate how multiple local SSDs affect the specific reservation request. Done means the cause of the insufficient-resource error is identified and the supported behavior or fix is documented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- google-cloud, kubernetes
- Domain
- cli, cloud
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100