-
Notifications
You must be signed in to change notification settings - Fork 486
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
GrafanaAgent API does not allow to limit resources of configReloader pods #5903
Comments
Adding output from
|
This issue has not had any activity in the past 30 days, so the |
Just to clarify, this only applies to the Operator in static mode; the Agent's own helm chart allows defining resources on the configReloader pod normally. |
This bothers me too, it would be great to be able to define resources for config-reloader too. |
As a workaround, one can create a |
What's wrong?
When grafana agent operator is deployed by a Helm chart into a namespace with a quota, the pods created by the operator fail the quota as no resources are applied to the config reloader pod spec.
The API should:
resources
consistently to all pods created by the agentSteps to reproduce
The error can be reproduced with loki helm chart, which creates a
GrafanaAgent
instance.ResourceQuota
loki-logs
created by the grafana agent operator fails quotaSystem information
Logs
The text was updated successfully, but these errors were encountered: