-
Notifications
You must be signed in to change notification settings - Fork 21
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
Standardize resource configuration #40
Conversation
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
/cc @mjudeikis |
front-proxy currently has hardcoded resource limits. worth changing as we going with it? |
Yes, absolutely. let me take care of it. |
Signed-off-by: Marvin Beckers <marvin@kubermatic.com>
@mjudeikis done, PTAL again! |
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mjudeikis The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
LGTM label has been added. Git tree hash: a95d9f70982e750b711875946e3da35fd323432c
|
I've never seen the way that the
kcp
Helm chart configures resources. This updatesvalues.yaml
and affected templates to use a de-facto standard for Helm charts, used in popular Helm charts like cert-manager or ingress-nginx.