-
Notifications
You must be signed in to change notification settings - Fork 226
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
Configurable resources for trident-operator #927
Labels
Comments
clementnuss
added a commit
to clementnuss/trident
that referenced
this issue
Sep 27, 2024
closes NetApp#927 Signed-off-by: Clément Nussbaumer <[email protected]>
clementnuss
added a commit
to clementnuss/trident
that referenced
this issue
Sep 27, 2024
closes NetApp#927 Signed-off-by: Clément Nussbaumer <[email protected]>
clementnuss
added a commit
to clementnuss/trident
that referenced
this issue
Oct 17, 2024
closes NetApp#927 Signed-off-by: Clément Nussbaumer <[email protected]>
clementnuss
added a commit
to clementnuss/trident
that referenced
this issue
Oct 17, 2024
closes NetApp#927 Signed-off-by: Clément Nussbaumer <[email protected]>
We continuously receive |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently there's no way to configure resources for trident-operator, e.g.
cpuLimit
of20m
seems to be too low and is causing cpu throttling.Proposed solution is to update
values.yaml
andtemplates/deployment.yaml
helm/trident-operator/templates/deployment.yaml:
helm/trident-operator/values.yaml:
The text was updated successfully, but these errors were encountered: