Skip to content

Kubernetes Secret size limit might not be enough to store Helm release #57

@ilya-lesikov

Description

@ilya-lesikov

Before proceeding

  • I didn't find a similar issue

Version

werf 2.8.0

How to reproduce

  1. Have a lot of resources in the chart.
  2. Do werf converge.

Result

Got error:

Secret "sh.helm.release.v1.(release-name).v1" is invalid: data: Too long: must have at most 1048576 character

Expected result

Release successful.

Additional information

Kubernetes resources, including Secrets, have size limit, which is configured per-cluster. The workaround is to split one release into multiple or change resource size limit cluster-wide.

The solution might be automatically splitting release Secret into multiple Secrets if we encounter such an error.

There is some work going on in upstream Helm: helm/helm#12277

Metadata

Metadata

Assignees

No one assigned

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions