-
Notifications
You must be signed in to change notification settings - Fork 384
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
feat: support HPA in helm chart #5127
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Dean Coakley <[email protected]>
Signed-off-by: Dean Coakley <[email protected]>
Signed-off-by: Dean Coakley <[email protected]>
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #5127 +/- ##
==========================================
- Coverage 66.87% 66.86% -0.02%
==========================================
Files 210 210
Lines 32977 32977
==========================================
- Hits 22054 22050 -4
- Misses 9588 9590 +2
- Partials 1335 1337 +2 ☔ View full report in Codecov by Sentry. |
thanks @Dean-Coakley this looks good ! can you add a test in https://github.com/envoyproxy/gateway/tree/main/test/helm |
{{ toYaml .Values.hpa.behavior | indent 4 }} | ||
{{- end }} | ||
metrics: | ||
{{- if .Values.hpa.targetCPU }} |
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.
Prefer to keep this entirely in values (similar to behavior) and not force end users to rely only on CPU/Mem. For example, custom metrics could be relevant here, e.g. size of the XDS cache, number of connected envoy proxies, etc.
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.
Ok, I will make this change.
Interesting, I was implementing this as an array initially: #4929 (comment)
But after looking around, I saw this different approach seemed more common so I thought I must be wrong:
- https://github.com/nginx/kubernetes-ingress/blob/main/charts/nginx-ingress/templates/controller-hpa.yaml#L24
- https://github.com/bitnami/charts/blob/main/bitnami/apache/templates/hpa.yaml#L23
- https://github.com/criblio/helm-charts/blob/master/helm-chart-sources/logstream-workergroup/templates/hpa.yaml#L28
But moving back to []
makes sense to me. And I have seen one example of doing similar:
If you get reports of usability issues you could follow a similar approach to traefik. Seems nice: https://github.com/traefik/traefik-helm-chart/blob/master/EXAMPLES.md#install-with-auto-scaling
What type of PR is this?
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes #4929
Release Notes: Yes