Alex Price
Alex Price
+1 I've run into this too. Would be great to get this working.
@nbrownus / @rawdigits / @IxDay I would love to see this PR merged as it will allow me to use go-audit in a project I am working on. What can...
@akshayks Thanks for using Escalator! It sounds like Escalator's current method for selecting nodes to terminate for scale down (oldest first) isn't the most ideal for your use case. #105...
We should be looking at performing a drain simulation to determine which nodes are the "easiest" to evict pods from and then terminate. This way we aren't wasting time trying...
I've created a seperate issue to look into different node selection methods for termination - https://github.com/atlassian/escalator/issues/105
Also needs to be included in the nodegroup objects too.
Related: https://github.com/containerd/containerd/issues/4937
Thanks for giving Escalator a go @FilipSwiatczak! Based on the following error: > `AccessDenied: User: arn:aws:sts::XXX:assumed-role/eksctl-bitbucketpipelines-nodegro-NodeInstanceRole-XXX is not authorized to perform: sts:AssumeRole on resource: arn:aws:iam::XXX:role/bitbucket-pipelines-escalator-role\n\tstatus code: 403` I'd say the...
I'd also like to mention that documentation on how to configure a role to another assume role is going to be missing from our documentation as it will depend on...
@FilipSwiatczak No problem! > So while this works, it's not fully automated as I can't find a way to fetch the sts role the pod starts under from the cluster....