envoyproxy / envoyproxy/gateway
gateway-crds-helm v1.4.0 install fails – rendered release exceeds 1 MiB Secret size limit
- Dominant language
- Go
- Stars
- 3k
- Forks
- 864
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 140
Description
*Description*:
When installing gateway-crds-helm v1.4.0 we hit:
```
Error: create: failed to create: Secret “sh.helm.release.v1.eg-crds.v1” is invalid: data: Too long: must have at most 1048576 bytes
```
Helm stores the whole rendered release in a single Secret. Kubernetes hard-limits any Secret to 1 MiB (1 048 576 bytes). Because this chart bundles ~40 Gateway-API CRDs, the compressed release record exceeds that limit and the API server rejects the Secret.
Expected behaviour: the chart should install cleanly, or the docs should tell users to apply the CRDs manually (`helm template | kubectl apply`).
*Repro steps*:
Install the gateway-crds-helm v1.4.0 chart with Helm (any install method). The install fails with the Secret size error above.
>**Note**: If there are privacy concerns, sanitize the data prior to
sharing.
*Environment*:
- gateway-crds-helm chart: v1.4.0
- helm: v3.17.3
- kubernetes: v1.31.6-gke
*Logs*:
```
Error: create: failed to create: Secret “sh.helm.release.v1.eg-crds.v1” is invalid: data: Too long: must have at most 1048576 bytes
```
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.