Support hyperkube

[lizrice]

Installed a new k8s cluster on Azure using the az acs CLI (as described here) and it's using hyperkube. This means the executable names are not quite as expected in the CIS Benchmark as the running processes are hyperkube <component> instead of kube-<component> - the output from ps below makes this more clear.

kube-bench should detect that it's hyperkube running (by running ps) and look for hyperkube as the executable it's looking for in different tests.

On the master node, output from ps -eaf | grep kube:

azureuser@k8s-master-xxxxxxxxx-0:~$ ps -eaf | grep kube
root      1622     1  0 08:35 ?        00:00:00 /usr/bin/docker run --net=host --pid=host --privileged --rm --volume=/dev:/dev --volume=/sys:/sys:ro --volume=/var/run:/var/run:rw --volume=/var/lib/docker/:/var/lib/docker:rw --volume=/var/lib/kubelet/:/var/lib/kubelet:shared --volume=/var/log:/var/log:rw --volume=/etc/kubernetes/:/etc/kubernetes:ro --volume=/srv/kubernetes/:/srv/kubernetes:ro gcrio.azureedge.net/google_containers/hyperkube-amd64:v1.6.6 /hyperkube kubelet --kubeconfig=/var/lib/kubelet/kubeconfig --require-kubeconfig --pod-infra-container-image=gcrio.azureedge.net/google_containers/pause-amd64:3.0 --address=0.0.0.0 --allow-privileged=true --enable-server --enable-debugging-handlers --pod-manifest-path=/etc/kubernetes/manifests --cluster-dns=10.0.0.10 --cluster-domain=cluster.local --register-schedulable=false --node-labels=role=master --cloud-provider=azure --cloud-config=/etc/kubernetes/azure.json --azure-container-registry-config=/etc/kubernetes/azure.json --hairpin-mode=promiscuous-bridge --network-plugin=kubenet --v=2
root      1805  1770  2 08:36 ?        00:01:36 /hyperkube kubelet --kubeconfig=/var/lib/kubelet/kubeconfig --require-kubeconfig --pod-infra-container-image=gcrio.azureedge.net/google_containers/pause-amd64:3.0 --address=0.0.0.0 --allow-privileged=


true --enable-server --enable-debugging-handlers --pod-manifest-path=/etc/kubernetes/manifests --cluster-dns=10.0.0.10 --cluster-domain=cluster.local --register-schedulable=false --node-labels=role=master --cloud-provider=azure --cloud-config=/etc/kubernetes/azure.json --azure-container-registry-config=/etc/kubernetes/azure.json --hairpin-mode=promiscuous-bridge --network-plugin=kubenet --v=2
root      2047  2030  0 08:36 ?        00:00:04 /hyperkube scheduler --kubeconfig=/var/lib/kubelet/kubeconfig --leader-elect=true --v=2
root      2155  2138  1 08:36 ?        00:00:59 /hyperkube controller-manager --kubeconfig=/var/lib/kubelet/kubeconfig --allocate-node-cidrs=True --cluster-cidr=10.244.0.0/16 --cluster-name=liz-k8s-cluster-liz-k8s-rg-49b47d --cloud-provider=azure --cloud-config=/etc/kubernetes/azure.json --root-ca-file=/etc/kubernetes/certs/ca.crt --service-account-private-key-file=/etc/kubernetes/certs/apiserver.key --leader-elect=true --v=2
root      2177  2160  1 08:36 ?        00:01:02 /hyperkube apiserver --admission-control=NamespaceLifecycle,LimitRanger,ServiceAccount,DefaultStorageClass,ResourceQuota --address=0.0.0.0 --allow-privileged --insecure-port=8080 --secure-port=443 --cloud-provider=azure --cloud-config=/etc/kubernetes/azure.json --service-cluster-ip-range=10.0.0.0/16 --etcd-servers=http://127.0.0.1:2379 --etcd-quorum-read=true --advertise-address=10.240.255.5 --tls-cert-file=/etc/kubernetes/certs/apiserver.crt --tls-private-key-file=/etc/kubernetes/certs/apiserver.key --client-ca-file=/etc/kubernetes/certs/ca.crt --service-account-key-file=/etc/kubernetes/certs/apiserver.key --storage-backend=etcd2 --v=4
root      2278  2263  0 08:36 ?        00:00:00 /bin/bash /opt/kube-addons.sh
root      2477  2462  0 08:36 ?        00:00:07 /hyperkube proxy --kubeconfig=/var/lib/kubelet/kubeconfig --cluster-cidr=10.244.0.0/16
azureus+  8538  8069  0 09:32 pts/0    00:00:00 grep --color=auto kube

[lizrice]

This is basically done, but doesn't work because of #29