Expose grafana as NodePort service and open it on k3d

[jkremser]

In order to improve the ux for Grafana, this PR exposes the grafana service as NodePort (30030 -> pod's 3000) and then on the k3d side we open port 3000 -> 30030 (similarly as for Prometheus, b/c there is a restriction that 30k < nodeport < ~32k).
Also changing the order in makefile: 1st deploy the grafana w/ the side-car that watches the configmaps and only then create the configmap (now w/ explicitly set namespace), because sometimes I hit a case when it wasn't picked up correctly

result: no need to run the kubectl port-forward and also setting the credentials to admin:admin, the web ui will ask to change it (before the change one had to run kubectl get secret --namespace k8gb grafana -o jsonpath="{.data.admin-password}" | base64 --decode ; echo)

cc @kuritka this is the follow-up we were talking about, I didn't want to complicate the previous PR w/ it

Signed-off-by: Jirka Kremser jiri.kremser@gmail.com

[k0da]

That reminds me we should probably finally switch to LB by default in Local setup

[kuritka]

@somaritane , I think it closes #120, WDYT ?

[somaritane]

@kuritka the idea of #120 was to have a publicly available dashboard for k8gb, published on https://grafana.com/grafana/dashboards/?orderBy=name&direction=asc with sample data.