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

Specify resource limits for audit and controller pod separately using helm values #869

Closed
RnkeZ opened this issue Oct 5, 2020 · 0 comments · Fixed by #874
Closed

Specify resource limits for audit and controller pod separately using helm values #869

RnkeZ opened this issue Oct 5, 2020 · 0 comments · Fixed by #874
Labels
enhancement New feature or request

Comments

@RnkeZ
Copy link
Contributor

RnkeZ commented Oct 5, 2020

Be able to specify resource limits for audit and controller pod separately using helm chart values
Currently controller-manager and audit are sharing same resources keys in chart values.yaml. They should be seperate since audit pod is often using more memory than controller-manager pod

Curent values for resources

resources:
  limits:
    cpu: 1000m
    memory: 512Mi
  requests:
    cpu: 100m
    memory: 256Mi

They should be more like this:

controller-manager:
    resources:
    limits:
        cpu: 1000m
        memory: 512Mi
    requests:
        cpu: 100m
        memory: 256Mi
audit:
    resources:
    limits:
        cpu: 1000m
        memory: 512Mi
    requests:
        cpu: 100m
        memory: 512Mi

Environment:

  • Gatekeeper version: 3.1.1
  • Kubernetes version: 1.17.5
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant