Helm 3.10: What's New, Release History & EOL Status

What’s new in Helm 3.10?

Which new CLI flags were introduced in Helm 3.10?

Three flags were added to give developers finer control over deployments and client behavior.

• --set-json – lets you pass a JSON string directly to helm install or helm upgrade.
• --no-headers – produces a raw list output without column headers, useful for scripting.
• --burst-limit – configures the client‑side request burst when talking to the Kubernetes API.

Example of the JSON flag:

helm install myapp ./chart --set-json '{"replicaCount":3,"service":{"type":"LoadBalancer"}}'

What improvements were made to existing commands?

The release refines several user‑facing commands and adds helpful metadata.

• OCI install now includes a concise description, making it easier to discover OCI‑based charts.
• New environment variables allow overriding TLS settings for the kube‑API without editing config files.
• StatefulSet readiness checks now emit clearer logs and avoid false‑positive readiness.

Which bugs were fixed in Helm 3.10?

Numerous edge‑case issues were addressed to improve stability.

• Special characters in filenames no longer break chart packaging.
• Release handling now validates array lengths, preventing panics on malformed releases.
• helm uninstall correctly deletes associated resources that were previously left behind.
• The JSON output of helm repo list now tolerates missing files without aborting.

What security‑related updates are included?

Dependency upgrades address known vulnerabilities and keep the tool aligned with recent Kubernetes releases.

• k8s client libraries updated to version 1.25, matching the latest API surface.
• Go runtime upgraded to 1.18, bringing compiler and runtime hardening.
• Third‑party packages such as testify and lib/pq were bumped to versions that fix CVE‑2022‑1996 and other issues.