Jordan Rodgers
Jordan Rodgers
Where in the docs should I add this? And what do you mean by "argumented"? Should I add another CLI flag that enables this?
We aren't using those instance types, so I don't think that is what is causing it (at least for us). We have ASGs with a mixed instance type policy and...
@x13n could this be caused by https://github.com/kubernetes/autoscaler/pull/5976 enabling parallel drain by default? I guess I could try 1.28 again with `-parallel-drain=false` to confirm 👀
Nope still hitting it, even with `--parallel-drain="false"`: ``` cluster-autoscaler-aws-6d95d65-hbgdb cluster-autoscaler I1115 19:34:18.815122 1 static_autoscaler.go:709] Decreasing size of build-32-128, expected=5 current=1 delta=-4 cluster-autoscaler-aws-6d95d65-hbgdb cluster-autoscaler E1115 19:34:18.815135 1 static_autoscaler.go:439] Failed to fix...
> Are there any updates on this issue with the new v2 improvements that have been merged since? Ah I see now, for anyone else that is slow like me...
Curious if https://github.com/Tinder/bazel-diff/pull/174 will solve this, might give it a try and see 👀
/remove-lifecycle rotten
Is there any timeline for this feature to get added? Using spot instances is extremely difficult right now without this feature along with https://github.com/kubernetes-sigs/cluster-api-provider-aws/issues/2574 when there are spot capacity constraints.
I'd love to see this fixed to include _all_ `ObjectMeta` fields, we're hitting this issue with `creationTimestamp`. I'm really curious what is excluding these fields from the generated CRDs?