github/k3s - k3s - https://git.xinac.net

Commit Graph

Author	SHA1	Message	Date
Brad Davidson	58315fe135	Set osImage for docker image Signed-off-by: Brad Davidson <brad.davidson@rancher.com>	3 years ago
Manuel Buil	a629db023c	Fail to start k3s if nm-cloud-setup is enabled Signed-off-by: Manuel Buil <mbuil@suse.com>	3 years ago
Brad Davidson	6c472b5942	Use zstd instead of gzip for embedded tarball Signed-off-by: Brad Davidson <brad.davidson@rancher.com>	4 years ago
JenTing Hsiao	57041f0239	Add codespell CI test and fix codespell error (#2740 ) * Add codespell CI test * Fix codespell error	4 years ago
Brad Davidson	ef9ad4f04d	Clean up CI warnings/errors Signed-off-by: Brad Davidson <brad.davidson@rancher.com>	4 years ago
Ranjib Dey	dcff6e7047	remove duplicate systemd directives Signed-off-by: Ranjib Dey ranjib@linux.com	4 years ago
Adam Farden	86d2e2a5f8	[systemd] really wait for network to come online (#1665 ) Wants= is required to actually set the dependency on network-online.service After= is required or k3s.service will be started at the same time as network-online.service In network environments with slow DHCP, both are required to ensure valid network configuration for k3s Signed-off-by: Adam Farden <adam@farden.cz>	4 years ago
Matthew Clive	fc55904d82	Add network dependency to installed service file (#2210 ) Adds the line `After=network-online.target` to the k3s systemd service file. This applies the fix mentioned in [this GH comment](https://github.com/rancher/k3s/issues/1626#issuecomment-642253812) which I can confirm makes k3s networking survive reboot in Raspbian Buster. [It appears, in some docs I found](https://www.digitalocean.com/community/tutorials/understanding-systemd-units-and-unit-files) that this is a recommended and usual way of specifying that we need the target to be _completed_ before starting k3s. Using just the `Wants=` directive doesn't work for this task, you have to add both directives at once to do this. Quote: > `Wants=`: This directive is similar to `Requires=`, but less strict. > `Systemd` will attempt to start any units listed here when this unit > is activated. If these units are not found or fail to start, the > current unit will continue to function. This is the recommended way to > configure most dependency relationships. Again, this implies a > parallel activation unless modified by other directives > [...] > `After=`: The units listed in this directive will be started before > starting the current unit. This does not imply a dependency > relationship and one must be established through the above > directives if this is required. - _(Emphasis mine)_ Signed-off-by: Matthew Clive <arcticlight@arcticlight.me> Signed-off-by: Brad Davidson <brad.davidson@rancher.com>	4 years ago
Brad Davidson	5ad76043ac	Replace unmount read loop with awk Signed-off-by: Brad Davidson <brad.davidson@rancher.com>	4 years ago
Patrick Force	8b47ccc4d1	2120: fix issue with umount arg list too long on uninstall Signed-off-by: Patrick Force <patrickforce@gmail.com>	4 years ago
Brad Davidson	1b78715903	Update base image version in Dockerfiles Should hopefully fix issues that cropped up with arm builds failing due to the sqlite libs from alpine 3.10 no longer being compatible with alpine edge, which was probably never a safe assumption to begin with. Signed-off-by: Brad Davidson <brad.davidson@rancher.com>	4 years ago
Adam Farden	b4335630b7	[systemd] Add value to LimitNOFILE due to performance problems When k3s is installed on an OS with default high ulimits, performance issues can be observed. This was discovered on CoreOS where the default value is 1073741816. Symptoms include very slow file operations such as installing a Rook/Ceph cluster will take ~6 hours instead of ~10 minutes. A google search for 'container LimitNOFILE' will show that most major projects set this already, including the (unused) containerd systemd unit found in this repository at /vendor/github.com/containerd/containerd/containerd.service k3OS is not affected becuasse the default there is already 1048576. See description in coreos/fedora-coreos-tracker#329	5 years ago
Viet Hung Nguyen	f741e8f9c5	Fix error when get version using Wget GitHub now returns lowercase: wget -SqO /dev/null https://github.com/rancher/k3s/releases/latest \|& grep -i location location: https://github.com/rancher/k3s/releases/tag/v1.17.3+k3s1	5 years ago
Erik Wilson	d15eb6aab6	Update RPM systemd services for easy modification. Modified installer produces a k3s-server and k3s-agent systemd service, with env files located in /etc/rancher/k3s. The k3s-server service may be started without modification but k3s-agent requires a token and url modification to the /etc/rancher/k3s/k3s-agent.env file for functionality. The k3s-server service will conflict with the k3s-agent service, so both may not be started at the same time. Creates ./package/rpm/ repo dir for rpm specific resources and relocates k3s.spec.	5 years ago
Erik Wilson	d578198ac0	Add rpm build & repo publish	5 years ago
Darren Shepherd	24fa3785a4	Include nsswitch so golang will read /etc/hosts file in docker container	5 years ago
Darren Shepherd	1429496b39	Add kubelet dir as volume in docker	5 years ago
William Zhang	635e1295c2	upgrade to go1.12.9 & alpine3.10 Signed-off-by: William Zhang <zhang.wanmin@zte.com.cn>	5 years ago
Erik Wilson	b87dd7c45a	Update Dockerfile to use bin/aux	6 years ago
Erik Wilson	02daa0b77f	Chmod /tmp to 1777 for e2e tests The kubernetes e2e tests will mount /tmp and verify permissions, fix to match the expectations of the test for our image.	6 years ago
Darren Shepherd	ce11c0f6f3	Get ARM CI working	6 years ago
Darren Shepherd	62c62cc7b4	Continued refactoring	6 years ago
Darren Shepherd	9bb7c27c62	Initial Commit	6 years ago

23 Commits (bcb662926d005dd65275bc462d4664ff5994ce07)