KH Chan

It should support all versions since HPA and custom metrics are supported.

Hi @turaleck, thanks for reporting this issue. May I know how are you assigning the credentials file? Is it from secrets or you generate that using an init container?

Hi, thanks for reporting the issue. However I am no longer with AWS and lost access to this repo. Please feel free to fork this project.

It does not work that way, at any one time there can only be one external metrics provider, that's why the last one takes over the API in your case....

the usage of configmap had been removed, which version are you using?

@lanecm do you mind checking if your `k8s-cloudwatch-adapter` deployment has reference to any configmaps? The reference to configmap was removed since 93feeca8ad3fc287ddcbb77edb32d782645d839d

By default the adapter will try to get the region from EC2 metadata API, unless you are getting metrics from a different region, you should not need to specify `AWS_REGION`

@lanecm seems like the adapter is trying to get configmap `extension-apiserver-authentication`, where was this defined?

@lanecm I've check the configs from other adapters as well, they all seems to be sharing the `extension-apiserver-authentication-reader`. Also checked in my cluster, the role `extension-apiserver-authentication-reader` has the policy rules...

Hi, thanks for reporting the issue. However I am no longer with AWS and lost access to this repo. Please feel free to fork this project.