Is there any guide for custom building k3s from source?

[Egg12138]

Is your feature request related to a problem? Please describe.
k3s is really great and portable. Now I am interested in HOW to make k3s binary and airgap images Smaller? In some edge case, 50Mb is intolerable. I wanna my edge device only serve as an agent, it doesn't need to controll the cluster.

Describe the solution you'd like

Is it possible to remove some components from k3s Embedded components? Can I leave only SQlite to store and remove Etcd?
Describe alternatives you've considered

Additional context
I am new to golang and cluster administration, so I have no idea from which I can do to custom the building process without making k3s unusable. Thankful to any suggestion.

[brandond]

If you're new to Go and Kubernetes, tinkering with K3s probably isn't where I would suggest starting out. There are a lot of moving pieces, and we wrap many projects which were not at all designed to be run together in a single process.

[Egg12138]

Really appreciate to your response. I was just wondering that is it possible to simply remove some components from k3s source in order to reduce the binary size. You mean that is it very difficult to get some component out of the k3s ?
Additionally, Is there any k3s custom building guideline? I wanna just slightly change something little. 😊

[dereknola]

I'm curious what devices you have in mind that makes 50MB of install size interolerable, but you have enough memory on the same device to actually run K3s. Our minimum resource usage for agents is 512MB of RAM. That's just to run a K3s agent, it doesn't include the RAM needed to actually run the workloads.