envoyproxy / envoyproxy/gateway

feat: Better Helm design

Abierto
#4,159 4 comentarios 0 reacciones 0 asignados Ver en GitHub
stale triage
Lenguaje dominante
Go
Estrellas
3k
Forks
864
Merge medio
2 d 2 h
PR fusionados (30 d)
140

Descripción

*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.

Guía de contribución

No hay ninguna guía de contribución indexada para este repositorio

Evaluación

Este issue todavía no se ha evaluado.

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.