-
Notifications
You must be signed in to change notification settings - Fork 4k
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
GCP: InstanceTemplates are no longer global
resources
#7396
Comments
Last night a node pool was upgraded to |
I've tried master, and even creating a new node spot node pool, and it looks like this is broken. The instanceTemplate regional logic is not being called correctly. |
/area provider/gce |
Same for k8s=1.29.9-gke.1177000 and ClusterAutoscaler appVersion=v1.29.3:
|
@x13n I attempted using CA 1.29 and encountered the same issue. |
It was backported but not released yet. The release is happening right now
- new CA patch versions for both 1.28 and 1.29 should work correctly with
regional templates.
|
Hi @4wdonny, the patch release for CA (1.28-1.31) is out. Could you please check if all things work fine? |
Which component are you using?:
Cluster Autoscaler
cluster-autoscaler
What version of the component are you using?: 1.29.4
Component version: 1.29.4
What k8s version are you using (
kubectl version
)?:v1.29.8-gke.1096000
kubectl version
OutputWhat environment is this in?: Google
GCP has changed the location of instance templates...they used to be Global and now they are regional. Is this configurable in the Autoscaler?
The text was updated successfully, but these errors were encountered: