-
Notifications
You must be signed in to change notification settings - Fork 345
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
allow setting resources & securityContext in Helm Chart values #3403
Conversation
As I don't know much about helm I cannot check if it's ok or not. Can anyone review this? @squakez @phantomjinx |
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.
Assuming this PR is fine, I think it's good to go ahead and merge it.
@squakez @phantomjinx Any objections?
Not familiar with Helm charts, hopefully @phantomjinx can have a look. |
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.
It would be nice to have some example of parameters to pass somewhere in the documentation.
@@ -79,6 +79,8 @@ Camel K chart and their default values. The chart allows configuration of an `In | |||
| `platform.build.registry.insecure` | Indicates if the registry is not secured | true | | |||
| `platform.cluster` | The kind of Kubernetes cluster (Kubernetes or OpenShift) | `Kubernetes` | | |||
| `platform.profile` | The trait profile to use (Knative, Kubernetes or OpenShift) | auto | | |||
| `operator.resources` | the resource requests and limits to use for the operator | | | |||
| `operator.securityContext` | The (container-related) securityContext to use for the operato | | |
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.
There is a typo
Let's merge for 1.10.0 |
one of the best practices for operating workloads in Kubernetes is to set resource requests and limits as well as securityContext related settings.
This PR introduces the possibility to set those resource requests and limits as well as securityContext related settings. Since the exact settings cant be known and depend on the environment as well as the number and complexity of camel routes, users will be able to freely define their settings in the
values.yaml
.Release Note