envoyproxy/gateway

Handling optionality for helm resources

Open

#7,750 opened on Dec 16, 2025

View on GitHub
 (2 comments) (0 reactions) (0 assignees)Go (802 forks)auto 404
help wanted

Repository metrics

Stars
 (2,871 stars)
PR merge metrics
 (Avg merge 14d 16h) (153 merged PRs in 30d)

Description

Description: Currently envoy gateway helm chart does not support optionality for the service account, cluster roles, cluster role bindings etc., there are use cases where the RBAC is handled outside the helm chart to avoid the dependency to the cluster admin access.

Contributor guide

Research direction
Examine the Helm chart templates for service account, cluster roles, and bindings. Add conditional `{{ if .Values.rbac.create }}` blocks to make them optional.
Tech stack
go
Domain
devopsinfrastructurecloud
Issue type
Feature
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
1-2 days
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
Active
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
Clear
Prerequisites
HelmKubernetes
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
40