Update Helm release longhorn to v1.7.0 #120
No reviewers
Labels
No labels
state
stale
state
to-do
state
waiting
system
argo
system
cni
system
dashboard
system
ingress
system
monitoring
system
sso
system
storage
system
woodpecker
type
bug
type
enhancement
type
update
type
dependency-dashboard
No milestone
No project
No assignees
3 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference: yolokube/core-deployments#120
Loading…
Reference in a new issue
No description provided.
Delete branch "renovate/longhorn-1.x"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
This PR contains the following updates:
1.6.2
->1.7.0
Release Notes
longhorn/charts (longhorn)
v1.7.0
Compare Source
Longhorn is a distributed block storage system for Kubernetes.
Configuration
📅 Schedule: Branch creation - At any time (no schedule defined), Automerge - At any time (no schedule defined).
🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.
♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.
🔕 Ignore: Close this PR and you won't be reminded about this update again.
This PR has been generated by Renovate Bot.
@aaron What do you think, is it still safe to merge?
https://longhorn.io/docs/1.7.0/important-notes/#unable-to-revert-a-volume-to-a-snapshot-created-before-longhorn-v170
@tom yes, since it only affects snapshots. We have external backups, which are fine.