envoyproxy/gateway

Helm chart `nameOverride` of Deployment/Service/ConfigMap/ServiceAccount, etc.

Open

#8,156 建立於 2026年2月2日

在 GitHub 查看
 (2 留言) (2 反應) (0 負責人)Go (802 fork)auto 404
help wanted

倉庫指標

Star
 (2,871 star)
PR 合併指標
 (PR 指標待抓取)

描述

The chart already implements the standard nameOverride and fullnameOverride helpers and also uses {{ include "eg.fullname" . }} to name some resources (for example all RBAC, the certgen and the topology injector components). However the "primary" resources like the Deployment, Service, ConfigMap, ServiceAccount, etc. are hardcoded to be named envoy-gateway. So it's a bit inconsistent and I'd like the ability to override the names of these resources too.

If we are to align with how most other charts do it, we would basically:

 apiVersion: apps/v1
 kind: Deployment
 metadata:
-  name: envoy-gateway
+  name: {{ include "eg.fullname" . }}
   namespace: '{{ .Release.Namespace }}'
 apiVersion: v1
 kind: ConfigMap
 metadata:
-  name: envoy-gateway-config
+  name: {{ include "eg.fullname" . }}-config
   namespace: '{{ .Release.Namespace }}'

I can submit a PR for this, if you're open to the idea!

貢獻者指南