- 18 Dec, 2019 5 commits
-
-
Erik Wilson authored
Fix missing version for tags
-
Erik Wilson authored
-
Erik Wilson authored
Apply containerd patch 3889
-
Erik Wilson authored
-
Erik Wilson authored
-
- 17 Dec, 2019 4 commits
-
-
Darren Shepherd authored
Cleanup k8s versioning
-
Darren Shepherd authored
Kine fix
-
Erik Wilson authored
-
Darren Shepherd authored
-
- 16 Dec, 2019 11 commits
-
-
Darren Shepherd authored
Small dqlite fixes
-
Darren Shepherd authored
-
Darren Shepherd authored
-
Erik Wilson authored
Upgrade k8s to v1.17.0
-
Erik Wilson authored
Set Wireguard keepalive to 25 seconds
-
Erik Wilson authored
-
Erik Wilson authored
-
Erik Wilson authored
-
Erik Wilson authored
-
Erik Wilson authored
-
Erik Wilson authored
-
- 13 Dec, 2019 5 commits
-
-
Erik Wilson authored
Remove docker-compose default token
-
Erik Wilson authored
-
Erik Wilson authored
Cleanup docker-compose.yml
-
Erik Wilson authored
Enable ip forwarding on both all and default net config
-
Erik Wilson authored
-
- 12 Dec, 2019 1 commit
-
-
Erik Wilson authored
-
- 11 Dec, 2019 6 commits
-
-
Erik Wilson authored
Allow --pause-image to set docker sandbox image also
-
Erik Wilson authored
Cleanup --flannel-backend help text
-
Erik Wilson authored
Upgrade go to 1.13.5
-
Erik Wilson authored
Mutable --node-label values for server/agent sub-commands.
-
Erik Wilson authored
For #577
-
Brennan Ashton authored
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>
-
- 10 Dec, 2019 4 commits
-
-
Erik Wilson authored
-
Erik Wilson authored
-
Erik Wilson authored
-
Erik Wilson authored
Update README.md: k3s does not exclude legacy/alpha/non-default features anymore
-
- 09 Dec, 2019 2 commits
-
-
Jacob Blain Christen authored
Values passed in via the server/agent `--node-label` flag are treated as mutable. They are passed through to the kubelet just as before but after the kubelet comes up they are applied again. This allows for passing labels a k3s start-time that may be necessary for scheduling but may change from boot to boot, e.g. `k3os.io/version` after an upgrade. Tested locallon on my amd64 workstation with the docker container. Addresses #1119.
-
Hyeon Kim authored
In the past, yes k3s did exclude all those legacy, alpha, non-default features from Kubernetes source as you can see in https://github.com/rancher/k3s/pull/113. But not anymore. As you can see in the source code, most of legacy/alpha/non-default features is available in k3s, and misleading README should be updated. But please, don't get me wrong. I'm actually glad to see those features enabled in k3s. :) Reference: https://github.com/kubernetes/kubernetes/compare/v1.16.3...rancher:v1.16.3-k3s.1
-
- 03 Dec, 2019 2 commits
-
-
Erik Wilson authored
Code cleanup
-
Erik Wilson authored
Bump dqlite to support arm 32-bit
-