Default Grafana Login rejected

[trahloff]

After I set up the services with kubectl apply --filename https://raw.githubusercontent.com/giantswarm/kubernetes-prometheus/master/manifests-all.yaml and tried to login with admin:admin I can't access the dashboard and get this error message (browser console):

Possibly unhandled rejection:
{
   "paths":[
      "/api",
      "/api/v1",
      "/apis",
      "/apis/apps",
      "/apis/apps/v1beta1",
      "/apis/authentication.k8s.io",
      "/apis/authentication.k8s.io/v1beta1",
      "/apis/authorization.k8s.io",
      "/apis/authorization.k8s.io/v1beta1",
      "/apis/autoscaling",
      "/apis/autoscaling/v1",
      "/apis/batch",
      "/apis/batch/v1",
      "/apis/batch/v2alpha1",
      "/apis/certificates.k8s.io",
      "/apis/certificates.k8s.io/v1alpha1",
      "/apis/extensions",
      "/apis/extensions/v1beta1",
      "/apis/policy",
      "/apis/policy/v1beta1",
      "/apis/rbac.authorization.k8s.io",
      "/apis/rbac.authorization.k8s.io/v1alpha1",
      "/apis/storage.k8s.io",
      "/apis/storage.k8s.io/v1beta1",
      "/healthz",
      "/healthz/poststarthook/bootstrap-controller",
      "/healthz/poststarthook/extensions/third-party-resources",
      "/healthz/poststarthook/rbac/bootstrap-roles",
      "/logs",
      "/metrics",
      "/swaggerapi/",
      "/ui/",
      "/version"
   ],
   "severity":"warning"
}

System:

Client Version: version.Info{Major:"1", Minor:"7", GitVersion:"v1.7.4", GitCommit:"793658f2d7ca7f064d2bdf606519f9fe1229c381", GitTreeState:"clean", BuildDate:"2017-08-17T08:48:23Z", GoVersion:"go1.8.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"5+", GitVersion:"v1.5.6-4+abe34653415733", GitCommit:"abe346534157336e6bd5a70702756cff19d43a49", GitTreeState:"clean", BuildDate:"2017-05-18T16:52:50Z", GoVersion:"go1.7.4", Compiler:"gc", Platform:"linux/amd64"}

[trahloff]

Solution:

enable Ingress to root path ("/").

It is not possible to access the Grafana UI through the kubectl proxy since it does not dynamically alter the login path. Maybe Include it in the documentation?

Can be closed.