-
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
opened Feb 28, 2025 by
lirtistan
Open
20
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
[Release-1.31] - Fallback to default registry endpoint is broken when using Issue is available to test only after we have an RC
"*"
wildcard mirror in registries.yaml with containerd 2.0
waiting-for-RC
[Release-1.32] - Fallback to default registry endpoint is broken when using Issue is available to test only after we have an RC
"*"
wildcard mirror in registries.yaml with containerd 2.0
waiting-for-RC
Fallback to default registry endpoint is broken when using This issue appears to be caused by an upstream bug
waiting-for-RC
Issue is available to test only after we have an RC
"*"
wildcard mirror in registries.yaml with containerd 2.0
kind/upstream-issue
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
Previous Next
ProTip!
Mix and match filters to narrow down what you’re looking for.