armhf (Raspberry Pi): AlertManager not ported yet

[openfaas]

armhf (Raspberry Pi): AlertManager not ported yet

[ecliptik]

Tested pull request #24 and it seems to fix this,

$ kubectl apply -f ./faas.armhf.yml,monitoring.armhf.yml,rbac.yml
service "faas-netesd" created                                                 
serviceaccount "faas-controller" created
deployment "faas-netesd" created
service "gateway" created
deployment "gateway" created
service "prometheus" created
deployment "prometheus" created
service "alertmanager" created
deployment "alertmanager" created
clusterrole "faas-controller" created
clusterrolebinding "faas-controller" created

$ kubectl get pods -o wide
NAME                            READY     STATUS    RESTARTS   AGE       IP           NODE
alertmanager-1828266779-zd7bb   1/1       Running   0          11s       10.244.2.8   tatl
faas-netesd-1317931779-1qwgx    1/1       Running   0          15s       10.244.2.6   tatl
gateway-1085489343-s0tnp        1/1       Running   0          14s       10.244.1.6   tael
prometheus-4259297277-h43rv     1/1       Running   0          13s       10.244.2.7   tatl

$ kubectl logs alertmanager-1828266779-zd7bb
time="2017-09-19T19:17:33Z" level=info msg="Starting alertmanager (version=0.5.1, branch=master, revision=0ea1cac51e6a620ec09d053f0484b97932b5c902)" source="main.go:101" 
time="2017-09-19T19:17:33Z" level=info msg="Build context (go=go1.7.3, user=root@fb407787b8bf, date=20161125-08:19:00)" source="main.go:102" 
time="2017-09-19T19:17:33Z" level=info msg="Loading configuration file" file="/etc/alertmanager/config.yml" source="main.go:195" 
time="2017-09-19T19:17:34Z" level=info msg="Listening on :9093" source="main.go:250"

[alexellis]

It's not just whether it loads in the cluster. The config is there to trigger auto-scaling into the Gateway. Are you sure the config has the correct rules? (maybe exec into the container and check)

[alexellis]

@ecliptik hey Michael.. pinging you for an answer ^

[alexellis]

Derek add label: hacktoberfest

[alexellis]

This should be fixed now through running in the new monitoring-config.armhf.yml file which bind-mounts the right config.