a952d5c32a
The Linux kernel is inconsistent about how devconf is configured for new network namespaces between ipv4 and ipv6. The behavior can also be controlled via net.core.devconf_inherit_init_net in Linux 5.1+ so make sure to enable forwarding on all and default for both ipv6 and ipv4. This issue first came up testing on a yocto kernel that had this patch: ipv4: net namespace does not inherit network configurations [0] https://www.kernel.org/doc/html/latest/admin-guide/sysctl/net.html#devconf-inherit-init-net [1] https://lkml.org/lkml/2014/7/29/119 Signed-off-by: Brennan Ashton <brennana@jfrog.com> |
||
|---|---|---|
| .github/ISSUE_TEMPLATE | ||
| cmd | ||
| contrib | ||
| e2e | ||
| manifests | ||
| package | ||
| pkg | ||
| scripts | ||
| tests/perf | ||
| vendor | ||
| .dockerignore | ||
| .drone.yml | ||
| .gitignore | ||
| .golangci.json | ||
| BUILDING.md | ||
| docker-compose.yml | ||
| Dockerfile.dapper | ||
| Dockerfile.sonobuoy.dapper | ||
| go.mod | ||
| go.sum | ||
| install.sh | ||
| k3s.service | ||
| LICENSE | ||
| main.go | ||
| Makefile | ||
| README.md | ||
| Vagrantfile | ||
| vendor.go | ||
k3s - 5 less than k8s
Lightweight Kubernetes. Easy to install, half the memory, all in a binary less than 40mb.
Great for:
- Edge
- IoT
- CI
- ARM
- Situations where a PhD in k8s clusterology is infeasible
What is this?
k3s is intended to be a fully compliant Kubernetes distribution with the following changes:
- Removed most in-tree plugins (cloud providers and storage plugins) which can be replaced with out of tree addons.
- Add sqlite3 as the default storage mechanism. etcd3 is still available, but not the default.
- Wrapped in simple launcher that handles a lot of the complexity of TLS and options.
- Minimal to no OS dependencies (just a sane kernel and cgroup mounts needed). k3s packages required
dependencies
- containerd
- Flannel
- CoreDNS
- CNI
- Host utilities (iptables, socat, etc)
Documentation
Please see the official docs site for complete documentation on k3s.
Quick-Start - Install Script
The k3s install.sh script provides a convenient way for installing to systemd or openrc,
to install k3s as a service just run:
curl -sfL https://get.k3s.io | sh -
A kubeconfig file is written to /etc/rancher/k3s/k3s.yaml and the service is automatically started or restarted.
The install script will install k3s and additional utilities, such as kubectl, crictl, k3s-killall.sh, and k3s-uninstall.sh, for example:
sudo kubectl get nodes
K3S_TOKEN is created at /var/lib/rancher/k3s/server/node-token on your server.
To install on worker nodes we should pass K3S_URL along with
K3S_TOKEN or K3S_CLUSTER_SECRET environment variables, for example:
curl -sfL https://get.k3s.io | K3S_URL=https://myserver:6443 K3S_TOKEN=XXX sh -
Manual Download
- Download
k3sfrom latest release, x86_64, armhf, and arm64 are supported. - Run server.
sudo k3s server &
# Kubeconfig is written to /etc/rancher/k3s/k3s.yaml
sudo k3s kubectl get nodes
# On a different node run the below. NODE_TOKEN comes from
# /var/lib/rancher/k3s/server/node-token on your server
sudo k3s agent --server https://myserver:6443 --token ${NODE_TOKEN}