envoyproxy / envoyproxy/gateway

feat: Better Helm design

Open
#4,159 4 comments 0 reactions 0 assignees View on GitHub
stale triage
Dominant language
Go
Stars
3k
Forks
864
Avg merge
2d 2h
Merged PRs (30d)
140

Description

*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: https://github.com/envoyproxy/gateway/blob/301eeddfa4c2f7e4e612874a9c5b13a976156c3e/internal/infrastructure/kubernetes/ratelimit/resource.go#L205 ) 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.

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.