-
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
cluster-autoscaler AWS "runtime error: invalid memory address or nil pointer dereference" #1556
Comments
you checked code in branch @losipiuk Any plan to release v1.2.4? Looks like still lots of kubernetes 1.10 users. I can help on the release. |
Here's the changes from 1.2.3 to current 1.2.x branch |
This comment has been minimized.
This comment has been minimized.
So far the CA lifecycle was the same as k8s. Therefore we consider CA 1.2 end-of-life (as k8s 1.10 is such). We were not planning on doing any official releases of CA from 1.2 branch. If I find some time today I can prepare a release though, yet without any strong guarantees as I do will not have time for thorough testing. @Jeffwan are all the changes you need already on 1.2 release branch? |
Released 1.2.4: https://github.com/kubernetes/autoscaler/releases/tag/1.2.4 |
Thanks @losipiuk and @aleksandra-malinowska. For new features, I won't expect to merge back to v1.2.x, new instance types are most needed. |
Change-Id: Iec0b9385e4fe847825441af175444717a3660f34
kubernete version: 1.10.11
ca version: 1.2.2
instance type: r5.large
this issue describes the problem being that the specific instance type isn't in the configuration, but looking into the
1.2.2
release i see that the instance type does indeed existfurthermore, from my testing, scaling up to 1 instance and scaling back down to 0 instances worked multiple times, so I'm not entirely sure what triggered this issue.
values.yaml
ca starts with the following flags:
ca logs:
The text was updated successfully, but these errors were encountered: