-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Scaler for Amazon managed service for Prometheus #2214
Comments
@ssaish make sense, are you wiling to conribute this feature? |
This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions. |
I would also love to see this, would be great to not need the proxy service recommended by aws as a workaround: https://aws.amazon.com/blogs/mt/proactive-autoscaling-kubernetes-workloads-keda-metrics-ingested-into-aws-amp/ |
We're happy to support it, fi somebody contributes it |
We already support Azure and GCP managed prometheus, so I guess that AWS one would be a nice addition. Recently we have migrated the AWS SDK from v1 to v2, so IIRC, there isn't blockers for moving forward |
Any update on this? |
Signed-off-by: Siva Guruvareddiar <gurusiva@amazon.com>
Incorporated the changes with SDK v2.. Added the unit and e2e tests.. Spinned up a new AWS AMP instance and the flow works good too.. can someone from Keda reviewer team help merge this PR for closure? |
I've posted some comments on that PR. Apart from that, could you update docs repo as well? (maybe you have already done it but I can't find the PR) |
Signed-off-by: Siva Guruvareddiar <gurusiva@gmail.com>
Signed-off-by: Siva Guruvareddiar <sivagurunath@gmail.com>
Signed-off-by: Siva Guruvareddiar <sivagurunath@gmail.com> Signed-off-by: Siva Guruvareddiar <gurusiva@amazon.com>
Signed-off-by: Siva Guruvareddiar <sivagurunath@gmail.com>
Signed-off-by: Siva Guruvareddiar <sivagurunath@gmail.com>
Signed-off-by: Siva Guruvareddiar <sivagurunath@gmail.com>
Signed-off-by: Siva Guruvareddiar <gurusiva@gmail.com> Signed-off-by: Siva Guruvareddiar <sivagurunath@gmail.com>
Signed-off-by: Siva Guruvareddiar <sivagurunath@gmail.com>
Signed-off-by: Siva Guruvareddiar <sivagurunath@gmail.com>
Signed-off-by: Siva Guruvareddiar <sivagurunath@gmail.com>
Signed-off-by: Siva Guruvareddiar <gurusiva@gmail.com> Signed-off-by: Siva Guruvareddiar <sivagurunath@gmail.com>
Signed-off-by: Siva Guruvareddiar <sivagurunath@gmail.com>
Signed-off-by: Siva Guruvareddiar <sivagurunath@gmail.com>
Signed-off-by: Siva Guruvareddiar <sivagurunath@gmail.com>
Signed-off-by: Siva Guruvareddiar <sivagurunath@gmail.com>
Signed-off-by: Siva Guruvareddiar <sivagurunath@gmail.com>
Signed-off-by: Siva Guruvareddiar <sivagurunath@gmail.com>
Signed-off-by: Siva Guruvareddiar <sivagurunath@gmail.com>
Signed-off-by: Siva Guruvareddiar <sivagurunath@gmail.com>
Signed-off-by: Siva Guruvareddiar <sivagurunath@gmail.com>
Signed-off-by: Siva Guruvareddiar <sivagurunath@gmail.com>
Proposal
AWS' managed solution for Prometheus lets customers ingest metrics without the need to manage environment. It would be nice to have a scaler support for Amazon Managed service for Prometheus
Use-Case
Amazon Managed Prometheus requires sigv4 authentication and the prometheus scaler currently does not support authentication parameters. Creating a scaler for Amazon Prometheus will give customers ability to scale the Kubernetes workloads by directly querying the metrics stored
Anything else?
No response
The text was updated successfully, but these errors were encountered: