Skip to content
This repository has been archived by the owner on Sep 24, 2021. It is now read-only.

k8s-cloudwatch-adapter to work with multiple regions #30

Open
romanudel opened this issue Apr 28, 2020 · 1 comment
Open

k8s-cloudwatch-adapter to work with multiple regions #30

romanudel opened this issue Apr 28, 2020 · 1 comment
Labels
enhancement New feature or request

Comments

@romanudel
Copy link

romanudel commented Apr 28, 2020 •
edited
Loading

Hi I've an EKS cluster that using HPA based on external metrics (the idea to use CRD resources) similar to what described here :
https://aws.amazon.com/blogs/compute/scaling-kubernetes-deployments-with-amazon-cloudwatch-metrics/
The setup i own is that SQS and the EKS are in two different regions which causing problem getting queries (seems that nothing is returned). is cloudwatch-adapter region dependent? if so what is the correct way to tell hpa where is SQS located( different region) inorder to get any results for that queue. I don't see any errors but hpa 'targets' remain 0 while the queue keep accumulate messages.
@chankh
Copy link
Contributor

chankh commented May 15, 2020

Yes, currently the adapter retrieves metrics from the region where it (and the EKS cluster) is running. This is a good feature suggestion, to be able to retrieve metrics from other regions.

@chankh chankh added the enhancement New feature or request label May 15, 2020
chankh added a commit that referenced this issue Aug 4, 2020
@chankh
Enable cross account and region support
bbbb01a 
Support cross account and region by specifying `roleArn` and `region`
respectively in the `externalmetric` spec definition. Using a `roleArn`
the adapter will assume into the specified role to retrieve metrics.

Issue: #8, #30
@rajeshkodali rajeshkodali mentioned this issue Aug 11, 2020
Merged
chankh added a commit that referenced this issue Sep 16, 2020
@chankh
Enable cross account and region support
eb50d57 
Support cross account and region by specifying `roleArn` and `region`
respectively in the `externalmetric` spec definition. Using a `roleArn`
the adapter will assume into the specified role to retrieve metrics.

Issue: #8, #30
chankh added a commit that referenced this issue Sep 16, 2020
@chankh
Make region and roleArn are optional
dc99029 
Issue: #8, #30
@chankh chankh mentioned this issue Sep 17, 2020
Merged
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
enhancement New feature or request
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
2 participants
@chankh @romanudel