See the release page for pre-built releases.
The clone will be much faster on this repo if you do
git clone --depth 1 https://github.com/rancher/k3s.git
This repo includes all of Kubernetes history so
--depth 1 will avoid most of that.
The k3s build process requires some autogenerated code and remote artifacts that are not checked in to version control. To prepare these resources for your build environment, run:.
mkdir -p build/data && ./scripts/download && go generate
To build the full release binary, you may now run
make, which will create
To build the binaries using without running linting (ie; if you have uncommitted changes):
If you make any changes to go.mod and want to update the vendored modules, you should run the following before runnining
go mod vendor && go mod tidy
The source code for Kubernetes is in
vendor/ and the location from which that is copied
./go.mod. Go to the referenced repo/tag and you'll find all the patches applied
to upstream Kubernetes.
：Code submit frequency
：React/respond to issue & PR etc.
：Well-balanced team members and collaboration
：Recent popularity of project
：Star counts, download counts etc.