Package Details: kubernetes-bin 1.13.2-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: duxet (icebal)
Last Packager: icebal
Votes: 11
Popularity: 1.586843
First Submitted: 2017-04-29 15:27
Last Updated: 2019-01-12 23:28

Dependencies (1)

Required by (11)

Sources (7)

Latest Comments

1 2 3 Next › Last »

icebal commented on 2019-01-12 23:29

missed that one, fixed and updated to 1.13.2 as well!

dschaefer79 commented on 2019-01-10 12:31

the sha512sums=('7b6a81c9f1b852b1e889c1b62281569a4b8853c79e5675b0910d941dfa7863c97f244f6d607aae3faf60bccd596dedb9d136b7fffeae199876e780904fd9f31e'

is wrong, I've modified it with this one


and makepkg -Acs and it's working

dschaefer79 commented on 2019-01-10 10:50


I try to update to kubernetes 1.13.1 and I have this error. Can someone help me ?

==> Validating source files with sha512sums... v1.13.1.tar.gz ... FAILED 0.7.0.tar.gz ... Passed kubernetes.install ... Passed ==> ERROR: One or more files did not pass the validity check! Error downloading sources: kubernetes-bin

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

icebal commented on 2018-12-10 19:17

ok, should be all better now!

icebal commented on 2018-12-01 10:03

@bobi, will do, i'll see if i can get it done in the next 24 hours!

bobi commented on 2018-11-29 12:03

For every arch, you should append the version number to the *server*.tar.gz archive to make it unique for each issue.

The reason for it is that, when working on a pre-existing building path that already contains a previous version of the archive, makepkg won’t download the last version and fail on checksum (or do worse things is checksum is skipped).

See the warning & solution here:

duxet commented on 2018-11-28 10:25

thanks! :)

icebal commented on 2018-11-28 10:24

arm changed to armv7l and armv7h, should be good now, tested on an armv7l board.

icebal commented on 2018-11-28 10:07

arm translates to armv7l and armv7h for arch, and arm64 is aarch64. you can check out my kubelet-bin package to see how i had to do it, not sure if armv7 will match to both types or not.

edit: just tried on an armv7l board, arm source doesn't match to armv7l :/ i'll update the PKGBUILD in a sec