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

RHCLOUD-34086 Configure CPU and Memory requests as variables #404

Merged
merged 5 commits into from
Oct 21, 2024

Conversation

Fynardo
Copy link
Contributor

@Fynardo Fynardo commented Oct 16, 2024

What?

Use vars to define CPU and Memory requests instead of hard-coded values

Why?

So we can configure CPU and Memory usage at deployment depending on env

@Fynardo Fynardo force-pushed the rhcloud-34086/adr-46-config branch from b457b93 to eec1daf Compare October 16, 2024 10:29
@@ -314,8 +314,12 @@ parameters:
value: INFO
- name: CPU_LIMIT
value: 500m
- name: CPU_REQUEST
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What if we need to increase the CPU or memory one of component without changing the others? Should we have more parameters?

Comment on lines 46 to 53
- name: EVENT_CONSUMER_CPU_REQUESTS
value: 100m
- name: EVENT_CONSUMER_CPU_LIMITS
value: 200m
- name: EVENT_CONSUMER_MEMORY_REQUESTS
value: 128Mi
- name: EVENT_CONSUMER_MEMORY_LIMITS
value: 256Mi
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Nitpick: keys could be singular instead of plural.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, lets be consistent in naming

Copy link
Contributor

@dehort dehort left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me!

@dehort dehort merged commit a7c5bdd into RedHatInsights:master Oct 21, 2024
12 of 15 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants