-
Notifications
You must be signed in to change notification settings - Fork 2.3k
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
etcd-snapshot prune does not load retention policy from config #9532
Milestone
Comments
Merged
This was referenced Mar 4, 2024
Validated using latest commit id 364dfd8 on master branchEnvironment DetailsInfrastructure Node(s) CPU architecture, OS, and Version:
Cluster Configuration: Config.yaml:
Steps to reproduce the issue and validate the fix
Results from reproducing the issue using k3s version v1.29.2+k3s1
Results from validation using k3s version v1.29.2+k3s-364dfd8b (364dfd8)
Passing either snapshot-retention: 2 and etcd-snapshot-retention: 2 retained the expected count of snapshots
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Environmental Info:
K3s Version:
k3s version v1.26.13+k3s2 (489d9b3)
go version go1.20.13
Node(s) CPU architecture, OS, and Version:
6.2.0-36-generic #37-Ubuntu SMP PREEMPT_DYNAMIC Wed Oct 4 10:14:28 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
Cluster Configuration:
1 server cluster
Describe the bug:
When running k3s etcd-snapshot prune would expect it to honor your snapshot retention that you have set in your config.
Steps To Reproduce:
etcd-snapshot-retention": 2
andsnapshot-retention: 2
in your configk3s etcd-snapshot prune
INFO[0000] Applying snapshot retention=5 to local snapshots with prefix on-demand in /var/lib/rancher/k3s/server/db/snapshots
Expected behavior:
The INFO message should have
snapshot retention=2
per what was set in the configActual behavior:
config is ignored and default of 5 is set
Additional context / logs:
Related PR: #9502
The text was updated successfully, but these errors were encountered: