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

[Release-1.29] - Bump containerd to v1.7.26 #11945

Closed
brandond opened this issue Mar 11, 2025 · 1 comment
Closed

[Release-1.29] - Bump containerd to v1.7.26 #11945

brandond opened this issue Mar 11, 2025 · 1 comment
Assignees
Milestone

Comments

@brandond
Copy link
Member

brandond commented Mar 11, 2025

We're bumping to containerd v2.0.3 on other branches, on this branch we just need latest 1.7.

No bugs to fix, just a version bump.

@brandond brandond self-assigned this Mar 11, 2025
@brandond brandond moved this from New to To Test in K3s Development Mar 11, 2025
@brandond brandond added this to the v1.29.15+k3s1 milestone Mar 11, 2025
@brandond brandond changed the title [Release-1.29] - Fallback to default registry endpoint is broken when using "*" wildcard mirror in registries.yaml with containerd 2.0 [Release-1.29] - Bump containerd to v1.7.26 Mar 11, 2025
@mdrahman-suse
Copy link

Validation on release-1.29 branch with commit 288efc5

Latest 1.7 https://github.com/containerd/containerd/releases/tag/v1.7.26

~> k3s -v
k3s version v1.29.14+k3s-288efc52 (288efc52)
go version go1.22.12

~> kubectl get node -o yaml | grep containerd -A1
      containerRuntimeVersion: containerd://1.7.26-k3s1
      kernelVersion: 5.14.21-150500.55.44-default

@github-project-automation github-project-automation bot moved this from To Test to Done Issue in K3s Development Mar 11, 2025
@mdrahman-suse mdrahman-suse self-assigned this Mar 11, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done Issue
Development

No branches or pull requests

2 participants