-
Notifications
You must be signed in to change notification settings - Fork 388
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
Add an option to configure HPA for the Envoy Gateway deployment in Helm #4929
Comments
Not sure I understand what is required here. Would it just be a case of adding something like?: diff --git a/charts/gateway-helm/values.tmpl.yaml b/charts/gateway-helm/values.tmpl.yaml
index cfcd9532..51517556 100644
--- a/charts/gateway-helm/values.tmpl.yaml
+++ b/charts/gateway-helm/values.tmpl.yaml
@@ -80,6 +80,16 @@ config:
controllerName: gateway.envoyproxy.io/gatewayclass-controller
provider:
type: Kubernetes
+ # envoyHpa:
+ # minReplicas: 2
+ # maxReplicas: 10
+ # metrics:
+ # - resource:
+ # name: cpu
+ # target:
+ # averageUtilization: 60
+ # type: Utilization
+ # type: Resource
logging:
level:
default: info And then if un-commented I think those entries would get pulled in by the templating in https://github.com/envoyproxy/gateway/blob/main/charts/gateway-helm/templates/envoy-gateway-config.yaml Or am I misunderstanding? |
the API would probably be at the top level similar to thedeployment and service field and would need a template similar to https://github.com/envoyproxy/gateway/blob/main/charts/gateway-helm/templates/envoy-gateway-deployment.yaml
|
Ah whoops, gotcha. I've started working on this. Based on the issue title "Add an option" I've put HPA behind a boolean.
Does that look reasonable enough? |
yeah that looks good @Dean-Coakley ! slight nit - prefer |
Description:
The text was updated successfully, but these errors were encountered: