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

Create Reasonable Resource Requests and Limits for CHT-Core-4.x #21

Open
henokgetachew opened this issue Aug 15, 2024 · 1 comment
Open

Comments

@henokgetachew
Copy link
Contributor

Right now the pods don't have resource limits and resource requests specified.

As a result we run into issues like these from time to time where the pods get evicted.

All pods need to specify sensible resource resource requests and resource constraints.

@henokgetachew
Copy link
Contributor Author

henokgetachew commented Aug 30, 2024

Additional information from this ticket.

The resource limits applied in that test are (For the couchdb pods):

      containers:
      - name: cht-couchdb-1
        image: public.ecr.aws/medic/cht-couchdb:4.2.0
        resources:
          requests:
            cpu: "1800m"    # About 23% of node CPU
            memory: "7Gi"   # About 24% of node memory
          limits:
            cpu: "2500m"    # About 32% of node CPU
            memory: "9Gi"   # About 31% of node memory

It probably makes sense to make these values configurable via values.yaml since it should depend from machine to machine and users might decide to make them higher/lower based on their own needs.

@henokgetachew henokgetachew moved this from Awaiting Triage to SRE Queue in Site Reliability Support Dashboard Oct 3, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Development

No branches or pull requests

1 participant