Skip to content

Add --release-name flag to dapr init and uninstall for Kubernetes - #1734

Open
cvas22 wants to merge 1 commit into
dapr:masterfrom
cvas22:feat/1115-helm-release-name
Open

cvas22 wants to merge 1 commit into
dapr:masterfrom
cvas22:feat/1115-helm-release-name

Conversation

@cvas22

@cvas22 cvas22 commented Oct 23, 2026

Copy link
Copy Markdown

Adds a --release-name flag to dapr init -k and dapr uninstall -k so the Helm release of the control plane no longer has to be called dapr (#1115). The default stays dapr, so nothing changes for existing users.

  • init: the release name is passed to Helm for the install. The chart pulled is still the dapr chart; I split the chart name from the release name in install, getVersion and getHelmChart, which used one constant for both.
  • uninstall: removes the release with the given name.
  • upgrade and renew-certificate already find the release by looking for the Dapr chart among the installed releases, so they work with a custom name without changes.

The new tests cover the default and custom name, and lookup of a custom-named release through an in-memory Helm store. go test ./pkg/kubernetes passes. I did not run the Kubernetes e2e tests since they need a cluster.

Fixes #1115

The Helm release name of the control plane was hardcoded to dapr. Allow
users to choose it with --release-name on init -k and uninstall -k.
upgrade and renew-certificate already look up the release by chart, so
they work with a custom name.

Fixes dapr#1115

Signed-off-by: Srinivas Chippagiri <cvas22@gmail.com>
@cvas22
cvas22 requested review from a team as code owners October 23, 2026 04:24
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Support custom helm release name

1 participant