Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Sidecar crashes when dapr operator is down in 1.3.0 #3665

Closed
artursouza opened this issue Sep 15, 2021 · 1 comment
Closed

Sidecar crashes when dapr operator is down in 1.3.0 #3665

artursouza opened this issue Sep 15, 2021 · 1 comment
Labels
kind/bug Something isn't working

Comments

@artursouza
Copy link
Member

In 1.3.0, when Dapr Operator is down (can be when upgrading to 1.4, for example), it causes all Dapr sidecars in the cluster to crash due to this change: 2a4fde2#diff-c4abdec7bd505d8a03b365a244374fd9cde3fd5b69976d463896b3d1c171772d

To workaround that, use 1.3.1 sidecar injector instead and perform a rolling restart of your deployments:

helm upgrade dapr dapr/dapr --set-string dapr_sidecar_injector.image.name=docker.io/daprio/daprd:1.3.1 -n dapr-system
kubectl rollout restart deploy/<name>
@artursouza artursouza added the kind/bug Something isn't working label Sep 15, 2021
@artursouza artursouza mentioned this issue Sep 15, 2021
Merged
7 tasks
@daixiang0
Copy link
Member

Fixed by #3666

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug Something isn't working
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
3 participants
@artursouza @wcs1only @daixiang0