Skip to content
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

Unable to Set Resources for JMX Exporter in Trino Helm Chart #202

Closed
alaturqua opened this issue Aug 7, 2024 · 1 comment · Fixed by #207
Closed

Unable to Set Resources for JMX Exporter in Trino Helm Chart #202

alaturqua opened this issue Aug 7, 2024 · 1 comment · Fixed by #207

Comments

@alaturqua
Copy link

alaturqua commented Aug 7, 2024

Issue: Unable to Set Resources for JMX Exporter in Trino Helm Chart

Description

Currently, the Trino Helm chart does not allow setting resource requests and limits for the JMX exporter. This limitation causes issues on Kubernetes clusters that require resource specifications for CPU and memory as a prerequisite.

Error Message

Error creating: pods "trino-helm-etl-coordinator-8655d99488-5jlwb" is forbidden: failed quota: quota-bitrino-dev: must specify limits.cpu for: jmx-exporter; limits.memory for: jmx-exporter; requests.cpu for: jmx-exporter; requests.memory for: jmx-exporter

Impact

This restriction prevents deployment on clusters with strict resource quota policies, hindering the ability to use the Trino Helm chart in such environments.

Suggested Solution

Please provide a way to configure resource requests and limits for the JMX exporter in the Helm chart values.

Tasks

No tasks being tracked yet.
@rotem-ad
Copy link
Member

We've also hit this issue. Opened a PR to resolve this

rotem-ad added a commit to rotem-ad/trino-charts that referenced this issue Sep 9, 2024
rotem-ad added a commit to rotem-ad/trino-charts that referenced this issue Sep 9, 2024
rotem-ad added a commit to rotem-ad/trino-charts that referenced this issue Sep 9, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

Successfully merging a pull request may close this issue.

2 participants