-
Notifications
You must be signed in to change notification settings - Fork 31
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
RHCLOUD-34086 Configure CPU and Memory requests as variables #404
Conversation
b457b93
to
eec1daf
Compare
deploy/clowdapp.yaml
Outdated
@@ -314,8 +314,12 @@ parameters: | |||
value: INFO | |||
- name: CPU_LIMIT | |||
value: 500m | |||
- name: CPU_REQUEST |
There was a problem hiding this comment.
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?
deploy/connect.yaml
Outdated
- 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 |
There was a problem hiding this comment.
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.
There was a problem hiding this comment.
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
There was a problem hiding this 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!
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