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.

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

Bump github.com/dapr/dapr from 1.14.0-rc.5 to 1.14.4 #630

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

dependabot[bot]
Copy link
Contributor

@dependabot dependabot bot commented on behalf of github Sep 17, 2024

Bumps github.com/dapr/dapr from 1.14.0-rc.5 to 1.14.4.

Release notes

Sourced from github.com/dapr/dapr's releases.

Dapr Runtime v1.14.4

Dapr 1.14.4

This update includes bug fixes:

Fixes being able to upgrade Dapr v1.14.x to v1.14.3 without manual intervention

Problem

When upgrading from Dapr versions v1.14.0, v1.14.1, or v1.14.2 to v1.14.3, the upgrade would fail with the following error.

Error: UPGRADE FAILED: cannot patch "dapr-scheduler-server" with kind StatefulSet: StatefulSet.apps "dapr-scheduler-server" is invalid: spec: Forbidden: updates to statefulset spec for fields other than 'replicas', 'ordinals', 'template', 'updateStrategy', 'persistentVolumeClaimRetentionPolicy' and 'minReadySeconds' are forbidden

The workaround for the user is to Delete the Scheduler StatefulSet before re-running the upgrade with the new storage size. The StorageClass must support volume expansion for this to work.

Impact

Users were unable to upgrade Dapr to v1.14.3 without manual intervention, breaking automated upgrades.

Root cause

In Dapr v1.14.3, the dapr-scheduler-server StatefulSet changed the default persistent volume request size from 1Gi to 16Gi. Kubernetes prevents updating this request field, resulting in this the above error.

Solution

This field has been reverted to the previous 1Gi request size. Users who wish to increase the volume size must follow the manual steps described in the documentation.

Fixes daprd not being able to connect to placement on k8s

Problem

When running dapr in high availability mode on Kubernetes, daprd would not be able to connect to the placement service after failure and re-election of a Placement leader.

Impact

The dapr sidecar would not be able to connect to the placement service, and would not be able to receive the actor placement tables.

Root cause

The connection to the failed placement leader was being properly closed, but not set to nil, so it was being reused.

Solution

... (truncated)

Commits

Dependabot compatibility score

You can trigger a rebase of this PR by commenting @dependabot rebase.


Dependabot commands and options

You can trigger Dependabot actions by commenting on this PR:

  • @dependabot rebase will rebase this PR
  • @dependabot recreate will recreate this PR, overwriting any edits that have been made to it
  • @dependabot merge will merge this PR after your CI passes on it
  • @dependabot squash and merge will squash and merge this PR after your CI passes on it
  • @dependabot cancel merge will cancel a previously requested merge and block automerging
  • @dependabot reopen will reopen this PR if it is closed
  • @dependabot close will close this PR and stop Dependabot recreating it. You can achieve the same result by closing it manually
  • @dependabot show <dependency name> ignore conditions will show all of the ignore conditions of the specified dependency
  • @dependabot ignore this major version will close this PR and stop Dependabot creating any more for this major version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this minor version will close this PR and stop Dependabot creating any more for this minor version (unless you reopen the PR or upgrade to it yourself)
  • @dependabot ignore this dependency will close this PR and stop Dependabot creating any more for this dependency (unless you reopen the PR or upgrade to it yourself)

Note
Automatic rebases have been disabled on this pull request as it has been open for over 30 days.

@dependabot dependabot bot requested review from a team as code owners September 17, 2024 16:24
@dependabot dependabot bot added the dependencies Pull requests that update a dependency file label Sep 17, 2024
@mikeee
Copy link
Member

mikeee commented Oct 23, 2024

@dependabot rebase

Bumps [github.com/dapr/dapr](https://github.com/dapr/dapr) from 1.14.0-rc.5 to 1.14.4.
- [Release notes](https://github.com/dapr/dapr/releases)
- [Changelog](https://github.com/dapr/dapr/blob/master/RELEASE.md)
- [Commits](dapr/dapr@v1.14.0-rc.5...v1.14.4)

---
updated-dependencies:
- dependency-name: github.com/dapr/dapr
  dependency-type: direct:production
  update-type: version-update:semver-patch
...

Signed-off-by: dependabot[bot] <[email protected]>
@dependabot dependabot bot force-pushed the dependabot/go_modules/github.com/dapr/dapr-1.14.4 branch from 3f1d181 to f7037b9 Compare October 23, 2024 10:32
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
dependencies Pull requests that update a dependency file
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant