You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We have moved to using GitOps to manage our deployments of system services, which means that ArgoCD is not creating a helm release. as it just does a helm template | kubectl apply -f .
Thus we should be able to use the dapr cli to run mtl renew-certificate and still have it restart everything we need.
Actual Behavior
It fails:
⌛ Starting certificate rotation
ℹ️ generating fresh certificates
ℹ️ Updating certifcates in your Kubernetes cluster
ℹ️ Dapr control plane version 1.14.4 detected in namespace dapr-system
❌ certificate rotation failed: could not find release name "dapr" in your helm releases
Steps to Reproduce the Problem
Create the yaml with helm template dapr dapr/dapr --set=global.ha.enabled=true | kubectl apply -f - and then try try and run the cli command to renew the cert.
Release Note
RELEASE NOTE:
The text was updated successfully, but these errors were encountered:
Expected Behavior
We have moved to using GitOps to manage our deployments of system services, which means that ArgoCD is not creating a helm release. as it just does a
helm template | kubectl apply -f .
Thus we should be able to use the dapr cli to run
mtl renew-certificate
and still have it restart everything we need.Actual Behavior
It fails:
Steps to Reproduce the Problem
Create the yaml with
helm template dapr dapr/dapr --set=global.ha.enabled=true | kubectl apply -f -
and then try try and run the cli command to renew the cert.Release Note
RELEASE NOTE:
The text was updated successfully, but these errors were encountered: