Package Details: k3s-bin 1.31.5+k3s1-1

Git Clone URL: https://aur.archlinux.org/k3s-bin.git (read-only, click to copy)
Package Base: k3s-bin
Description: Lightweight Kubernetes
Upstream URL: https://k3s.io
Keywords: kubernetes
Licenses: Apache
Conflicts: k3s, k3s-git
Submitter: duxet
Maintainer: galdor
Last Packager: galdor
Votes: 26
Popularity: 0.45
First Submitted: 2019-02-28 07:14 (UTC)
Last Updated: 2025-02-16 08:41 (UTC)

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 Next › Last »

francescortiz commented on 2021-10-03 10:43 (UTC)

Why don't you include k3s-killall.sh like https://aur.archlinux.org/packages/k3s-1.22-bin/ does?

galdor commented on 2021-09-27 09:06 (UTC)

Updated to 1.22.2.

galdor commented on 2021-09-17 14:44 (UTC)

Updated to 1.21.4.

k8ie commented on 2021-03-16 10:17 (UTC)

@txomon Oh yeah! Please add the backup line, that would really avoid many headaches.

txomon commented on 2021-03-16 09:42 (UTC) (edited on 2021-03-16 10:08 (UTC) by txomon)

I would recommend to just copy the original to /etc/systemd/system/k3s.service replacing there k3s server with k3s agent.

Also, please update the PKGBUILD to include a backup line like amiga23 said https://aur.archlinux.org/packages/k3s-bin/#comment-748864

k8ie commented on 2021-02-18 15:31 (UTC)

@Vanilla Thanks, I also started using systemctl edit so the edits survive updates. It still seems kind of hacky tho.

Vanilla commented on 2021-02-18 13:11 (UTC) (edited on 2021-02-18 13:44 (UTC) by Vanilla)

@satcom886

<del>I notice the k3s.service.env installed inside /etc/systemd/system. According to the Getting Started section of the K3S docs, by specifying K3S_URL and K3S_TOKEN, the K3S can be instructed to run in agent mode. (Not tried yet.)</del>

I was wrong. That trick is only for its installation script instead of the K3S binary. In order to run a K3S agent, now I have to partially overwrite the shipped service file with systemctl edit k3s.service .

galdor commented on 2021-01-05 06:21 (UTC)

Would it be possible to add a k3s group and use it for /etc/rancher/k3s/k3s.yaml ? In the current state, the file is owned by root and is 0600, but this file must be readable by any kubernetes tool such as kubectl.

k8ie commented on 2020-12-06 09:46 (UTC)

I have a possibly dumb question, but how do you "oficially" choose between server and agent mode?

I edited /usr/lib/systemd/system/k3s.service and replaced k3s server with k3s agent. I'm guessing that this is not the right way...

i.further commented on 2020-11-16 15:33 (UTC)

The some files is not removed when it removed.

« First ‹ Previous 1 2 3 4 5 6 Next › Last »