The option --no-deploy was deprecated by
0374c4f63d
and is now replaced in the install.sh documentation by --disable
Signed-off-by: omichaelis <38879457+oliviermichaelis@users.noreply.github.com>
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
The command rm -f will succeed even if run for a file that does not
exist. Hence it is superfluous to existence check a file that we want
to purge with rm -f, which makes the script a bit simpler to read.
Change-Id: If4eafea568301f418e0dd533e7175781ebf6000a
Signed-off-by: Joakim Roubert <joakimr@axis.com>
Moving symlinks to containerd to a for loop makes maintenance easier.
It also reveals a duplicate, redundant, rm -rf build/data and one
duplicate, redundant, rm -rf bin/kubectl, that can be both be purged.
Change-Id: Id81a05dcf2dadcc60ef8171494a284fbe1630400
Signed-off-by: Joakim Roubert <joakim.roubert@axis.com>
Moving symlinks to containerd to a for loop makes maintenance easier;
also using the -f flag for ln rather than having a separate rm step.
It also reveals a duplicate, redundant, rm -rf build/data and one
duplicate, redundant, rm -rf bin/kubectl, that can be both be purged.
Signed-off-by: Joakim Roubert <joakim.roubert@axis.com>
