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
Hi, I've been using Escalator so far for scaling k8s clusters with Spark batch jobs running inside. Thanks for building an awesome product!
I'm currently running Kubernetes cluster with Kops+Kiam which do not have any issue about assuming IAM role for Escalator pod, but when I try to run Escalator on EKS-managed cluster, it can't assume IAM role given by service account.
The root cause is that older version of AWS SDK does not support iam:AssumeRoleWithWebIdentity with OIDC provider. it seems resolvable when we update AWS SDK to the latest version - 1.23.13 is the minimum verison required.
It will be greatly appreciated if the new version with updated SDK is released. Thank you so much!
The text was updated successfully, but these errors were encountered:
Hi, I've been using Escalator so far for scaling k8s clusters with Spark batch jobs running inside. Thanks for building an awesome product!
I'm currently running Kubernetes cluster with Kops+Kiam which do not have any issue about assuming IAM role for Escalator pod, but when I try to run Escalator on EKS-managed cluster, it can't assume IAM role given by service account.
The root cause is that older version of AWS SDK does not support iam:AssumeRoleWithWebIdentity with OIDC provider. it seems resolvable when we update AWS SDK to the latest version - 1.23.13 is the minimum verison required.
It will be greatly appreciated if the new version with updated SDK is released. Thank you so much!
The text was updated successfully, but these errors were encountered: