Enable prometheus on arm64 architecture

[balchua]

The enable script will use the following multi-arch images:

• gcr.io/k8s-staging-kube-state-metrics/kube-state-metrics:v1.9.7 instead of quay.io/coreos/kube-state-metrics:v1.9.5
• quay.io/brancz/kube-rbac-proxy:v0.8.0 instead of quay.io/coreos/kube-rbac-proxy:v0.4.1

The image quay.io/brancz/kube-rbac-proxy:v0.8.0 is also referenced now in the kube-prometheus master branch. The image is referenced from the author of the kube-rbac-proxy repository.

Tested it in AWS arm EC2 and it is looking good.

ubuntu@ip-172-31-18-25:~$ uname -a
Linux ip-172-31-18-25 5.4.0-1029-aws #30-Ubuntu SMP Tue Oct 20 10:08:09 UTC 2020 aarch64 aarch64 aarch64 GNU/Linux
ubuntu@ip-172-31-18-25:~$ kubectl -n monitoring get pods -o wide
NAME                                  READY   STATUS    RESTARTS   AGE   IP             NODE              NOMINATED NODE   READINESS GATES
prometheus-operator-58fc7fbbd-rrnx8   2/2     Running   0          25m   10.1.215.41    ip-172-31-18-25   <none>           <none>
node-exporter-l8z2b                   2/2     Running   0          25m   172.31.18.25   ip-172-31-18-25   <none>           <none>
prometheus-adapter-557648f58c-2h47x   1/1     Running   0          25m   10.1.215.45    ip-172-31-18-25   <none>           <none>
kube-state-metrics-54d8bdf4db-7ndvx   3/3     Running   0          25m   10.1.215.44    ip-172-31-18-25   <none>           <none>
alertmanager-main-0                   2/2     Running   0          25m   10.1.215.42    ip-172-31-18-25   <none>           <none>
prometheus-k8s-0                      3/3     Running   1          25m   10.1.215.46    ip-172-31-18-25   <none>           <none>
grafana-7c9bc466d8-2dt2m              1/1     Running   0          25m   10.1.215.43    ip-172-31-18-25   <none>           <none>
ubuntu@ip-172-31-18-25:~$ 

[balchua]

Finally tested the PR on a mix arch cluster.

Nodes:

• ip-172-31-30-155 - arm64 architecture
• ip-172-31-30-209- amd64 architecture
• ip-172-31-20-99 - amd64 architecture

ubuntu@ip-172-31-30-155:~$ uname -m
aarch64
ubuntu@ip-172-31-30-155:~$ microk8s kubectl get pods -A -o wide 
NAMESPACE     NAME                                      READY   STATUS    RESTARTS   AGE   IP              NODE               NOMINATED NODE   READINESS GATES
kube-system   calico-kube-controllers-847c8c99d-lqhhb   1/1     Running   0          40m   10.1.175.65     ip-172-31-30-209   <none>           <none>
kube-system   calico-node-hr46w                         1/1     Running   0          19m   172.31.20.99    ip-172-31-20-99    <none>           <none>
kube-system   calico-node-cq4zp                         1/1     Running   0          21m   172.31.30.209   ip-172-31-30-209   <none>           <none>
monitoring    prometheus-adapter-557648f58c-8xgvc       1/1     Running   0          17m   10.1.90.193     ip-172-31-20-99    <none>           <none>
monitoring    node-exporter-pbjwn                       2/2     Running   0          17m   172.31.30.209   ip-172-31-30-209   <none>           <none>
monitoring    node-exporter-smzsd                       2/2     Running   0          17m   172.31.20.99    ip-172-31-20-99    <none>           <none>
monitoring    node-exporter-wtk8r                       2/2     Running   2          17m   172.31.30.155   ip-172-31-30-155   <none>           <none>
monitoring    kube-state-metrics-54d8bdf4db-sptvd       3/3     Running   3          17m   10.1.2.137      ip-172-31-30-155   <none>           <none>
monitoring    prometheus-operator-58fc7fbbd-6kflg       2/2     Running   2          17m   10.1.2.135      ip-172-31-30-155   <none>           <none>
kube-system   coredns-86f78bb79c-7tfj8                  1/1     Running   1          18m   10.1.2.136      ip-172-31-30-155   <none>           <none>
kube-system   calico-node-7h5nn                         1/1     Running   1          21m   172.31.30.155   ip-172-31-30-155   <none>           <none>
monitoring    alertmanager-main-0                       2/2     Running   2          17m   10.1.2.139      ip-172-31-30-155   <none>           <none>
monitoring    prometheus-k8s-0                          3/3     Running   4          17m   10.1.2.140      ip-172-31-30-155   <none>           <none>
monitoring    grafana-7c9bc466d8-p9f6f                  1/1     Running   1          17m   10.1.2.138      ip-172-31-30-155   <none>           <none>
ubuntu@ip-172-31-30-155:~$ 

All pods are all in running state. I can also access grafana too.

[balchua]

Fixes #1204

[ktsakalozos]

LGTM +1 thank you @balchua