You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When enabling node autoprovisioning, the service account for it stays at "default" and nodes in "automatic" node pools have no rights on Google APIs (e.g. pull from private GCR)
I would have expected that the service account would be set to the same one that is created for the "regular" node pools so that pods scheduled or rescheduled on the automatic node pools would work the same (at least by default).
I believe it is in auto_provisioning_defaults.service_account
The text was updated successfully, but these errors were encountered:
In my testing, it seems like NAP wouldn't create any new Node Pools until I went into the web UI for my Terraformed cluster and selected a Service Account in the Node Auto-Provisioning section. I couldn't actually find any errors in the logs, it just wouldn't do anything no matter what I tried. Just mentioning this for anyone else who is similarly stumped.
I would love this to work, so I will attempt a PR if I can figure it out.
When enabling node autoprovisioning, the service account for it stays at "default" and nodes in "automatic" node pools have no rights on Google APIs (e.g. pull from private GCR)
I would have expected that the service account would be set to the same one that is created for the "regular" node pools so that pods scheduled or rescheduled on the automatic node pools would work the same (at least by default).
I believe it is in auto_provisioning_defaults.service_account
The text was updated successfully, but these errors were encountered: