-
Notifications
You must be signed in to change notification settings - Fork 2.4k
Issues: k3s-io/k3s
Fallback to default registry endpoint is broken when using `"...
#11857
by lirtistan
was closed Mar 19, 2025
Closed
22
Executables from k3s maybe be incorrectly flagged as malware
#9738
by benklett
was closed Mar 14, 2024
Closed
19
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
K3s cannot be installed using https://get.k3s.io because sha256sum-amd64.txt cannot be found
#11974
opened Mar 16, 2025 by
supriyo-biswas
K3s exits due to containerd exiting with This issue appears to be caused by an upstream bug
failed to recover state: failed to get metadata for stored sandbox
error
kind/upstream-issue
Multi-arch image manifests are not built for release candidates
#11971
opened Mar 14, 2025 by
brooksn
[Release-1.32] - Cannot enable 1.32 feature gates: agent kubelet emulated version 1.31
kind/bug
Something isn't working
Cannot enable 1.32 feature gates: agent kubelet emulated version 1.31
kind/bug
Something isn't working
Add a notice to the K3s documentation, if someone is trying to use a galera cluster as datastore
#11816
opened Feb 19, 2025 by
lirtistan
Dual-stack Networking documentation should include the need for --node-ip listing both host IP versions
#11735
opened Feb 9, 2025 by
kable-wilmoth
k3s + tailscale + dual-stack ipv6 doesn't start with tailscale advertise-routes error
status/stale
#11572
opened Jan 12, 2025 by
m00nwtchr
Previous Next
ProTip!
Find all open issues with in progress development work with linked:pr.