Skip to content
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

Open
s0uky opened this issue Sep 4, 2024 · 3 comments
Open

feat: Better Helm design #4159

s0uky opened this issue Sep 4, 2024 · 3 comments
Labels

Comments

@s0uky
Copy link

s0uky commented Sep 4, 2024

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:

) and consolidate them into a single location. This improves maintainability over Helm chart.

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.

@s0uky s0uky added the triage label Sep 4, 2024
@zirain
Copy link
Contributor

zirain commented Sep 4, 2024

prom-statd-exporter issue tracked here.

@s0uky
Copy link
Author

s0uky commented Sep 5, 2024

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.

@zirain
Copy link
Contributor

zirain commented Sep 5, 2024

indeed we should, that's a huge gap between rerfect and real.
any controbutions around this is welcome.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants