Is there issue created or discussion yet about supporting the new k8s component config files? Ref: • kubelet ◦ https://kubernetes.io/docs/reference/command-line-tools-reference/kubelet/ ◦ https://kubernetes.io/docs/tasks/administer-cluster/kubelet-config-file/ ◦ https://github.com/kubernetes/kubernetes/blob/master/cmd/kubelet/app/options/options.go#L88 • kube-scheduler ◦ https://kubernetes.io/docs/reference/command-line-tools-reference/kube-scheduler/ ◦ https://github.com/kubernetes/kubernetes/blob/master/cmd/kube-scheduler/app/options/options.go#L66 • kube-proxy ◦ https://kubernetes.io/docs/reference/command-line-tools-reference/kube-proxy/ ◦ https://github.com/kubernetes/kubernetes/blob/master/cmd/kube-proxy/app/server.go#L97 • kube-cloud-controller-manager ◦ Unclear, the API seems to support config file but couldn’t find documentation ◦ https://github.com/kubernetes/cloud-provider/blob/master/config/types.go#L85 • kube-controller-manager ◦ no planned config file adoption yet (?) ◦ https://kubernetes.io/docs/reference/command-line-tools-reference/kube-controller-manager/ ◦ https://github.com/kubernetes/kubernetes/blob/master/cmd/kube-controller-manager/app/options/options.go • kube-apiserver ◦ no planned config file adoption yet (?) ◦ https://kubernetes.io/docs/reference/command-line-tools-reference/kube-apiserver/ ◦ https://github.com/kubernetes/kubernetes/blob/master/cmd/kube-apiserver/app/options/options.go

Looks like this slack channel isn't that active. Anyone working on the github issue "imeout in k3s while pulling big images (2.3Gb)" here https://github.com/rancher-sandbox/rancher-desktop/issues/2479 trying to find collaborators...

Nope, nobody working on it. Most likely because it's not something that k3s has total control over. Probably a kubelet or containerd thing.

@wooden-autumn-36808 has left the channel

Hi. Any suggestions about good-first-issue I can take? Thx in advance.

Is this https://github.com/k3s-io/k3s/issues/3404 something I can take care of as first issue to fix?

Hey Folks! Just a quick question as I couldn't find any issues opened or closed related to this. Is there any specific reason for k3s to not support the devmapper snapshotter?

@bland-kilobyte-1588 has left the channel

Hey all! Not sure if this is the correct channel for this question but thought I'd give it a shot. If there's a better place for me to ask this please let me know. I'm directing this primarily at Rancher/K3s employees/maintainers. I recently put together a GitHub Action for installing and starting a K3s server node and I'm getting ready to open source the project. I was wondering if the K3s team would be interested in accepting this project as a donation. I'd be happy to continue to maintain it but it might be a better fit if it lived under k3s-io. I haven't open sourced it yet because I want to make sure licensing is hammered out beforehand if the K3s team is interested. I'm happy to add any Rancher/K3s people to the repo if you'd like to see it. Also, just to note. It's totally OK if the answer to this is "no". I just thought I'd throw the idea out there. If I don't hear back or the answer is indeed "no" I'll open source the project under MIT, add it to the GitHub Marketplace and post a link.

Hi, I created a minimal read-only registry server for k3s, I'm not sure whether you'd want this contribution, or how to include it. The k3s patch is minimal (~25 lines) and I can create a pull request, but it requires a support script to populate the registry and documentation. My change his here: https://github.com/k3s-io/k3s/compare/master...adrianmoye:k3s:ADD_REGISTRY and an example with documentation is here: https://github.com/adrianmoye/minimal-registry . If you're interested please can somebody help?

Hi Everyone, I am studying the code of k3s and I am trying to figure out the purpose of the Fill inserts found in the code The database has many of these gap records inserted: What is their purpose? Can I safely disable the code that inserts them?