Package Details: k3s-bin 1.30.3+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.20
First Submitted: 2019-02-28 07:14 (UTC)
Last Updated: 2024-08-21 07:51 (UTC)

Latest Comments

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

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.

amiga23 commented on 2020-06-02 07:04 (UTC)

Please do not override the config file during update.

backup=("etc/systemd/system/k3s.service.env")

mercutio commented on 2020-02-04 10:29 (UTC)

I updated the package to 1.17.2, in case someone else might find it useful: https://gist.github.com/mercutiodesign/e871496deca3002fbe7086355772d974

tbrock commented on 2020-01-03 22:27 (UTC)

It looks like that commit did update them, the shas must have changed since the initial publish. Anyway, they are correct now. Enjoy!

tbrock commented on 2020-01-03 19:26 (UTC)

Ah I'm sorry I use a script that runs updpkgsums and it must not have updated all of them for some reason, I just published a pkgrel 2 verson that should do the trick.

isra17 commented on 2020-01-03 14:55 (UTC)

valid sha (From my result and as advertisied in the sha256sum-amd64.txt) is c7c5d39a60fa0665913f83cee78eb0c440cbd7c9e2e85783f10a2bba09d977ee

isra17 commented on 2020-01-03 14:50 (UTC)

Source k3s-1.0.1-x86_64 does not pass validity test anymore.

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