SeeRepo
Draw my repo

What is k3s built with?

k3s is a Go repo built with net/http and k8s.io/apiserver. It stores its data in etcd, go.etcd.io/etcd/client/v3, go.etcd.io/etcd/server/v3, and go.etcd.io/etcd/client/pkg/v3, is tested with github.com/onsi/gomega, github.com/onsi/ginkgo/v2, Uber, github.com/stretchr/testify, and github.com/go-test/deep, deploys with github.com/sirupsen/logrus, containerd, Kubernetes, k8s.io/klog/v2, Prometheus, and 12 more, and uses github.com/ipfs/go-ds-leveldb and MinIO. It has 61,448 written lines, with 107 test files.

Read on November 7, 2026, at commit dca306c. Read it as markdown

Backend

The base 1

Data 5

  • etcd5 files
  • go.etcd.io/etcd/client/v33 files
  • go.etcd.io/etcd/server/v33 files
  • go.etcd.io/etcd/client/pkg/v32 files
  • github.com/ipfs/go-ds-leveldb1 file

Services 1

Support

The base 1

  • k8s.io/apiserver17 files

Testing 5

  • Uber6 files
  • github.com/stretchr/testify4 files
  • github.com/onsi/gomega56 files
  • github.com/onsi/ginkgo/v253 files
  • github.com/go-test/deep1 file

Deploy 17

5 more
  • github.com/natefinch/lumberjack2 files
  • go.uber.org/zap2 files
  • github.com/ipfs/go-log/v21 file
  • github.com/Microsoft/hcsshim1 file
  • k8s.io/kube-proxy1 file

Tools 5

  • github.com/urfave/cli/v238 files
  • go.etcd.io/etcd/etcdutl/v31 file
  • golang.org/x/mod1 file
  • k8s.io/cli-runtime1 file
  • k8s.io/kubectl1 file

Other 45

  • Google4 files
  • github.com/distribution/reference2 files
  • github.com/moby/sys/userns2 files
  • github.com/opencontainers/go-digest2 files
  • github.com/containerd/cgroups/v31 file
  • github.com/containerd/containerd/api1 file
  • github.com/containerd/errdefs1 file
  • github.com/google/go-containerregistry1 file
  • github.com/google/renameio/v21 file
  • github.com/google/uuid1 file
  • github.com/gorilla/websocket1 file
  • github.com/inetaf/tcpproxy1 file
33 more
  • github.com/moby/sys/reexec1 file
  • github.com/opencontainers/cgroups1 file
  • github.com/opencontainers/image-spec1 file
  • github.com/opencontainers/selinux1 file
  • k8s.io/apimachinery58 files
  • k8s.io/api34 files
  • k8s.io/client-go29 files
  • k8s.io/utils19 files
  • golang.org/x/sys11 files
  • k8s.io/component-base10 files
  • github.com/otiai10/copy4 files
  • github.com/rootless-containers/rootlesskit/v34 files
  • gopkg.in/yaml.v24 files
  • k8s.io/cri-api3 files
  • k8s.io/cri-client3 files
  • sigs.k8s.io/yaml3 files
  • github.com/libp2p/go-libp2p2 files
  • github.com/robfig/cron/v32 files
  • github.com/yl2chen/cidranger2 files
  • golang.org/x/crypto2 files
  • golang.org/x/sync2 files
  • github.com/blang/semver/v41 file
  • github.com/dustin/go-humanize1 file
  • github.com/fsnotify/fsnotify1 file
  • github.com/joho/godotenv1 file
  • github.com/json-iterator/go1 file
  • github.com/klauspost/compress1 file
  • github.com/spf13/afero1 file
  • github.com/spf13/pflag1 file
  • github.com/vishvananda/netlink1 file
  • golang.org/x/net1 file
  • k8s.io/apiextensions-apiserver1 file
  • k8s.io/component-helpers1 file

Other repos with a similar stack

Ordered by how much of its stack they share with k3s, then by stars.

Frequently asked questions

What language is k3s written in?
k3s is written in Go, with 61,448 written lines.
What framework does k3s use?
k3s is built with net/http and k8s.io/apiserver.
What database does k3s use?
k3s stores its data in etcd, go.etcd.io/etcd/client/v3, go.etcd.io/etcd/server/v3, and go.etcd.io/etcd/client/pkg/v3.
What services does k3s use?
k3s uses github.com/ipfs/go-ds-leveldb and MinIO.
Does k3s have tests?
Yes. k3s has 107 test files and is tested with github.com/onsi/gomega, github.com/onsi/ginkgo/v2, Uber, github.com/stretchr/testify, and github.com/go-test/deep.
Which repos have a stack like k3s's?
The ones that share most of its stack:labring/sealoscontainerd/containerdpingcap/tidb

See inside your code, today.

Paste your repo and see it drawn, part by part: a medium one in under a minute.

Free, no account.

Or look inside SeeRepo's own →

Is it your repo? Add its badge, keep it up to date or take it down →