-
Notifications
You must be signed in to change notification settings - Fork 524
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
helm: promote autoscaling to stable #7368
Comments
@dimitarvdimitrov if you want, you can assign me to both of these issues. #7368 & #7367 |
thanks @beatkind 🙏 I'm not sure of the level of detail in these issues, so ask away if anything isn't 100% clear |
Some thoughts on
Basically drills down to have a global section for kedaAutoscaling:
prometheusAddress: http://...
customHeaders:
{}
pollingInterval: 10 |
@dimitarvdimitrov is there an issue to add hpa to the components that do not have it yet like the ingester? |
for ingesters I could only find an internal one unfortunately - grafana/mimir-squad#1410. I see that @jhalterman was last working on that. Jonathan is there a public issue for this work? |
The issue you cited is the only one. There's nothing public yet. |
#7282 added autoscaling to Helm as an experimental feature. This issue is about remaining work in order to promote autoscaling to stable.
Bugs
Docs/Migration procedure
Remote URL UX
kedaAutoscaling
section #7392X-Scope-OrgID: metamonitoring
if the config is already sending metrics to the same Mimir installation (the same way that metamonitoring computes it)Helm-jsonnet diffing
Make dashbaords compatible with helm-deployed KEDA objects
/operations/mixin
changes in feat(helm): add keda autoscaling and fix dashboards #4687 - the matchers for keda objects should allow for helm-deployed objectsThe text was updated successfully, but these errors were encountered: