Skip to content

[Backport release-1.6] fix(velero): apply CRD updates on upgrade via CreateReplace - #3728

Merged
myasnikovdaniil merged 1 commit into
release-1.6from
backport-3727-to-release-1.6
Aug 18, 2026
Merged

[Backport release-1.6] fix(velero): apply CRD updates on upgrade via CreateReplace#3728
myasnikovdaniil merged 1 commit into
release-1.6from
backport-3727-to-release-1.6

Conversation

@github-actions

Copy link
Copy Markdown

Description

Backport of #3727 to release-1.6.

velero evolves its CRD schema between versions; v1.18 adds the Queued
and ReadyToStart backup phases. Helm never upgrades CRDs shipped in
crds/, the generated HelmRelease left spec.upgrade.crds at the Skip
default, and the package disables the chart's upgrade-crds Job, so live
CRDs stayed frozen at first-install state: the server upgrades, the
apiserver rejects the new phases, and backups sit in New while the
HelmRelease stays green. Opt the velero PackageSource into
CreateReplace, consistent with mongodb-operator, add a platform test
pinning the policy, and correct the stale Job-disable rationale in the
package.

Assisted-By: Claude <noreply@anthropic.com>
Signed-off-by: Aleksei Sviridkin <3811295@gmail.com>
(cherry picked from commit f4d812c)
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.

2 participants