Package Details: kubernetes-bin 1.15.0-0

Git Clone URL: (read-only)
Package Base: kubernetes-bin
Description: Production-Grade Container Scheduling and Management - binary version.
Upstream URL:
Keywords: kubernetes
Licenses: Apache
Conflicts: kubeadm-bin, kubeadm-git, kubectl, kubectl-bin, kubelet-bin, kubernetes
Provides: hyperkube, kube-apiserver, kube-controller-manager, kube-proxy, kube-scheduler, kubeadm, kubectl, kubelet, kubernetes
Submitter: moscar
Maintainer: lrustand
Last Packager: lrustand
Votes: 14
Popularity: 1.325278
First Submitted: 2017-04-29 15:27
Last Updated: 2019-07-20 16:15

Dependencies (1)

Required by (21)

Sources (7)

Pinned Comments

tunggad commented on 2018-12-26 12:27

To save you time searching the net for solutions why your kubeadm init could not run successfully, it complains about kubelet, that it is not running or not healthy. This AUR package is not intented to use kubeadm init to setup a cluster, it's intention to setup a cluster from scratch, where all control plane components (kube-apiserver, kube-scheduler, kube-controller-manager) and kube-proxy run as systemd service. But in a cluster setup by kubeadm init these components will be deployed as Pods (kube-system Pods). So if you want to use this AUR package to setup a cluster with kubeadm init, do the followings tweaks:

I tried to mimic the unit file and the drop-in file /etc/systemd/system/kubelet.service.d/10-kubeadm.conf, normally available in DEB or RPM package of other distros, but missing in this AUR package, changing the systemd unit file and it's referenced EnvironmentFiles. The result looks like that:

--- /usr/lib/systemd/system/kubelet.service ---


Description=Kubernetes Kubelet Server


[Service] WorkingDirectory=/var/lib/kubelet








--- EnvironmentFile: /etc/kubernetes/config ---

logging to stderr means we get it in the systemd journal


journal message level, 0 is debug


--- EnvironmentFile: /etc/kubernetes/kubelet ---

KUBELET_ARGS="--bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --cgroup-driver=cgroupfs --network-plugin=cni"

systemctl status kubelet should look like that:

● kubelet.service - Kubernetes Kubelet Server Loaded: loaded (/usr/lib/systemd/system/kubelet.service; enabled; vendor preset: disabled) Active: active (running) since Sun 2018-12-23 22:54:48 UTC; 11h ago Docs: Main PID: 325 (kubelet) Tasks: 24 (limit: 4915) Memory: 119.3M CGroup: /system.slice/kubelet.service └─325 /usr/bin/kubelet --logtostderr=true --v=0 --bootstrap-kubeconfig=/etc/kubernetes/bootstrap-kubelet.conf --kubeconfig=/etc/kubernetes/kubelet.conf --config=/var/lib/kubelet/config.yaml --cgroup-driver=cgroupfs --network-plugin=cni

Run daemon-reload for the above changes to take effects

systemctl daemon-reload

Disable all of the following systemd services installed by this AUR package:

systemctl disable kube-apiserver
systemctl disable kube-controller-manager
systemctl disable kube-scheduler
systemctl disable kube-proxy

======> NOW YOU ARE FINE TO execute #kubeadm init

Without these tweaks your kubeadm init would not be able to start the kubelet.service it needs to setup the cluster for the first time and CNI networking addons (Calico or Flannel) would not work.

Also switch off all swap partitions if you have any, otherwise kubelet would not start! #sudo swapoff -a

Latest Comments

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

icebal commented on 2018-11-22 07:55

i have a ton of arm devices, all running arch, @duxcet, if you need to test out the PKGBUILDs, as well as x86_64 arch devices.

duxet commented on 2018-11-21 06:15

@icebal thanks, i've added you as co-maintainer and i've also updated a list of conflicting packages

@kiden i will try to add support for ARM this week

icebal commented on 2018-11-21 01:20

also, i'd be down to co-maintain if duxet needs help.

icebal commented on 2018-11-21 01:17

good call, i have added the provides and conflicts to my packages, will try to get a hold of duxet and see if he can update the PKGBUILD.

the difference between the packages is this also has the apiserver binary, hyperkube, etc, that are not needed for dev/homelab/small prod clusters, whereas the kubelet-bin and kubeadm-bin are all you need for barebones k8s.

pschichtel commented on 2018-11-13 12:51

How does this package compare to kubelet-bin + kubectl-bin + kubeadm-bin ? Either way there should probably be Provides and Conflicts to those packages given that they overlap a lot.

klden commented on 2018-11-11 06:21

+1 for arm and arm64

icebal commented on 2018-10-05 10:18

Any way we can add the arm and arm64 versions? They already release the binaries, so it shouldnt be too hard to add arm for armv7l and armv7h, and arm64 for aarch64.

rryan commented on 2018-09-29 05:46

Thanks for this! It looks like the man pages all say the same thing:

This file is autogenerated, but we’ve stopped checking such files into the repository to reduce the need for rebases. Please run hack/generate‐ to populate this file.

Is there any way to fix that?

jesusofsuburb1a commented on 2018-09-28 08:14

PKGBUILD breaks for 1.12, since the binary kube-aggregator is no longer part of kubernetes (obsolete).

Removing kube-aggregator from the binaries in package() is enough to make it work.

See the release notes for confirmation: (ctrl+f 'kube-aggregator')

moscar commented on 2017-11-29 11:37

I'm disowning this as I don't use it anymore and don't want to maintain it.