-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Can't Add GPU Accelerator to Node Pool part of Regional Cluster #263
Comments
Went over the code and looks like the problem is that node pool doesn't accept a location. What ever location is specified in the cluster is used directly in the node pool. I've created a branch with some changes but while testing I can't seem to even get the cluster to create using the master branch. For some reason the cluster gets created with an error code 13 with the message INTERNAL(not very helpful), then proceeds to deleting the cluster. |
Can you share the docs you're referring to? If you're able to get this working even via gcloud that would help. |
FYI, node pool node locations (that are different than the cluster's default node locations) will be supported as part of the next provider release: GoogleCloudPlatform/magic-modules#2320 |
Interesting, I didn't know we supported the ability to run different node pools in different locations. Looks like we should be able to add this with the next provider release, thanks for the heads up! |
Ah, makes sense. For some reason when I read the description of location in the docs, I assumed you could specify something other than the clusters location. Even though it clearly says |
@DanielWozniak Likely 2-3 weeks, depending on when the provider release lands. |
Sounds good. In the meantime I suppose we can close this issue. |
Hi All, Since the feature has been released in version 2.16.0 could I request this be added to the module. I've tried working on this myself however for some reason im not even able to create a simple cluster before even adding any changes I get a simple
For some reason after 20 seconds of trying to create the cluster it just starts deleting itself, without giving any helpful message of why this is happening. |
@DanielWozniak Is this no longer needed? |
It's still needed, just thought that since this issue is tagged with |
Ok I've marked it as an Enhancement. We'll put it in our backlog. |
I've actually moved this into #290. |
I currently have a regional cluster. For this cluster I would like to create a new node pool which contains a GPU accelerator. The problem with this is that in the google documentation it states:
For regional clusters that run GPUs, there is currently no region which has any GPU type in three zones. If you want to run GPUs in a regional cluster, you need to specify zones using the --node-locations flag
When I specify the location in the module like so
For some reason the location is not getting picked up and in the plan we get:
Even after running the apply it still doesn't get picked up and the following error gets thrown:
Would this be a bug in the module? Or is there something that I might be missing?
The text was updated successfully, but these errors were encountered: