-
Notifications
You must be signed in to change notification settings - Fork 328
-
Notifications
You must be signed in to change notification settings - Fork 328
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: Better Helm design #4159
Labels
Comments
prom-statd-exporter issue tracked here. |
Yes, I know about the issue with statsd. My point was it's not good to hardcode any configuration which could be done through Helm. |
indeed we should, that's a huge gap between rerfect and real. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description:
The official Helm chart for the Gateway component should be more robust and comprehensive. Currently, it seems to lack resources for managing deployments of GatewayClass, Gateway, and other child objects associated with CRDs. Values file should be more configurable.
Extract all Kubernetes resource definitions related to the Gateway component from the source code (like this example with statsd:
gateway/internal/infrastructure/kubernetes/ratelimit/resource.go
Line 205 in 301eedd
Ideally, the Helm chart should provide a single point of control to manage the creation and configuration of GatewayClass, Gateway, and other related CRD objects.
The text was updated successfully, but these errors were encountered: