Charts: [stable/kubernetes-dashboard] Can't login with ingress

Created on 30 Apr 2019  路  4Comments  路  Source: helm/charts

Is this a request for help?:

I used stable/kubernetes-dashboard can't login with ingress, but kubectl is working.

Is this a BUG REPORT or FEATURE REQUEST? (choose one):

Version of Helm and Kubernetes:
Kubernetes:
Client Version: version.Info{Major:"1", Minor:"13", GitVersion:"v1.13.1", GitCommit:"eec55b9ba98609a46fee712359c7b5b365bdd920", GitTreeState:"clean", BuildDate:"2018-12-13T19:44:19Z", GoVersion:"go1.11.2", Compiler:"gc", Platform:"darwin/amd64"}
Server Version: version.Info{Major:"1", Minor:"10", GitVersion:"v1.10.11", GitCommit:"637c7e288581ee40ab4ca210618a89a555b6e7e9", GitTreeState:"clean", BuildDate:"2018-11-26T14:25:46Z", GoVersion:"go1.9.3", Compiler:"gc", Platform:"linux/amd64"}

Helm:
Client: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}
Server: &version.Version{SemVer:"v2.13.1", GitCommit:"618447cbf203d147601b4b9bd7f8c37a5d39fbb4", GitTreeState:"clean"}

Which chart:
stable/kubernetes-dashboard

What happened:
I used stable/kubernetes-dashboard can't login with ingress, but kubectl proxy is working.

What you expected to happen:
Use a custom domain to access the dashboard.

kubectl proxy

kubectl proxy

http://localhost:8001/api/v1/namespaces/kube-system/services/https:dashboard-kubernetes-dashboard:https/proxy/#!/overview?namespace=default

dashboard values

ingress:
  ## If true, Kubernetes Dashboard Ingress will be created.
  ##
  enabled: true

  ## Kubernetes Dashboard Ingress annotations
  ##
  annotations:
    kubernetes.io/ingress.class: nginx
  #   kubernetes.io/tls-acme: 'true'
  ## If you plan to use TLS backend with enableInsecureLogin set to false
  ## (default), you need to uncomment the below.
  ## If you use ingress-nginx < 0.21.0
  #   nginx.ingress.kubernetes.io/secure-backends: "true"
  ## if you use ingress-nginx >= 0.21.0
    nginx.ingress.kubernetes.io/backend-protocol: "HTTPS"


  ## Kubernetes Dashboard Ingress paths
  ##
  paths:
    - /
  #  - /*

  ## Kubernetes Dashboard Ingress hostnames
  ## Must be provided if Ingress is enabled
  ##
  hosts:
    - dashboard.etby.studio

  ## Kubernetes Dashboard Ingress TLS configuration
  ## Secrets must be manually created in the namespace
  ##
  # tls:
  #   - secretName: kubernetes-dashboard-tls
  #     hosts:
  #       - kubernetes-dashboard.domain.com

## Serve application over HTTP without TLS
enableInsecureLogin: false

rbac:
  # Specifies whether RBAC resources should be created
  create: true

  # Specifies whether cluster-admin ClusterRole will be used for dashboard
  # ServiceAccount (NOT RECOMMENDED).
  clusterAdminRole: true

  # Start in ReadOnly mode.
  # Only dashboard-related Secrets and ConfigMaps will still be available for writing.
  #
  # Turn OFF clusterAdminRole to use clusterReadOnlyRole.
  #
  # The basic idea of the clusterReadOnlyRole comparing to the clusterAdminRole
  # is not to hide all the secrets and sensitive data but more
  # to avoid accidental changes in the cluster outside the standard CI/CD.
  #
  # Same as for clusterAdminRole, it is NOT RECOMMENDED to use this version in production.
  # Instead you should review the role and remove all potentially sensitive parts such as
  # access to persistentvolumes, pods/log etc.
  clusterReadOnlyRole: false

nginx-ingress log

- [192.168.65.3] - - [30/Apr/2019:04:46:00 +0000] "POST /api/v1/login HTTP/1.1" 200 1468 "http://dashboard.etby.studio/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36" 1479 0.004 [kube-system-dashboard-kubernetes-dashboard-443] 10.1.0.60:8443 1468 0.000 200 c7542269f12f7ca65799ac384b2a49fc
192.168.65.3 - [192.168.65.3] - - [30/Apr/2019:04:46:00 +0000] "GET /api/v1/login/status HTTP/1.1" 200 93 "http://dashboard.etby.studio/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36" 403 0.054 [kube-system-dashboard-kubernetes-dashboard-443] 10.1.0.60:8443 93 0.060 200 d55e0cd29924bf9b9f34554cae9b8666
192.168.65.3 - [192.168.65.3] - - [30/Apr/2019:04:46:00 +0000] "GET /api/v1/csrftoken/login HTTP/1.1" 200 87 "http://dashboard.etby.studio/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36" 406 0.001 [kube-system-dashboard-kubernetes-dashboard-443] 10.1.0.60:8443 87 0.010 200 cff65624ed15270f37eb9ffe0c54baa7
192.168.65.3 - [192.168.65.3] - - [30/Apr/2019:04:46:00 +0000] "POST /api/v1/login HTTP/1.1" 200 1465 "http://dashboard.etby.studio/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36" 1479 0.006 [kube-system-dashboard-kubernetes-dashboard-443] 10.1.0.60:8443 1465 0.010 200 6452525bfdbcd621c8a8756fb9f56bf9
192.168.65.3 - [192.168.65.3] - - [30/Apr/2019:04:46:00 +0000] "GET /api/v1/login/status HTTP/1.1" 200 93 "http://dashboard.etby.studio/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36" 403 0.002 [kube-system-dashboard-kubernetes-dashboard-443] 10.1.0.60:8443 93 0.010 200 1618b307f75a6a547f2a5f316908192c
192.168.65.3 - [192.168.65.3] - - [30/Apr/2019:04:46:00 +0000] "GET /api/v1/csrftoken/login HTTP/1.1" 200 87 "http://dashboard.etby.studio/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36" 406 0.071 [kube-system-dashboard-kubernetes-dashboard-443] 10.1.0.60:8443 87 0.070 200 13048efadf7fe67a21af4228885691be
192.168.65.3 - [192.168.65.3] - - [30/Apr/2019:04:46:00 +0000] "POST /api/v1/login HTTP/1.1" 200 1466 "http://dashboard.etby.studio/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36" 1479 0.007 [kube-system-dashboard-kubernetes-dashboard-443] 10.1.0.60:8443 1466 0.010 200 52f22c1f3858c08561c6270d940327f8
192.168.65.3 - [192.168.65.3] - - [30/Apr/2019:04:46:00 +0000] "GET /api/v1/login/status HTTP/1.1" 200 93 "http://dashboard.etby.studio/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36" 403 0.001 [kube-system-dashboard-kubernetes-dashboard-443] 10.1.0.60:8443 93 0.000 200 dacf507689ee6f4171a83d9984d3f969
192.168.65.3 - [192.168.65.3] - - [30/Apr/2019:04:46:00 +0000] "GET /api/v1/csrftoken/login HTTP/1.1" 200 87 "http://dashboard.etby.studio/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36" 406 0.002 [kube-system-dashboard-kubernetes-dashboard-443] 10.1.0.60:8443 87 0.000 200 912f672fe80902722f5a59756e9e485a
192.168.65.3 - [192.168.65.3] - - [30/Apr/2019:04:46:00 +0000] "POST /api/v1/login HTTP/1.1" 200 1467 "http://dashboard.etby.studio/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36" 1479 0.004 [kube-system-dashboard-kubernetes-dashboard-443] 10.1.0.60:8443 1467 0.000 200 076e644790f49196922e65b854adb09b
192.168.65.3 - [192.168.65.3] - - [30/Apr/2019:04:46:00 +0000] "GET /api/v1/login/status HTTP/1.1" 200 93 "http://dashboard.etby.studio/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36" 403 0.006 [kube-system-dashboard-kubernetes-dashboard-443] 10.1.0.60:8443 93 0.000 200 2d890131a3a4e05c92c6c14ab5db1160
192.168.65.3 - [192.168.65.3] - - [30/Apr/2019:04:46:41 +0000] "GET /api/v1/csrftoken/login HTTP/1.1" 200 87 "http://dashboard.etby.studio/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36" 406 0.046 [kube-system-dashboard-kubernetes-dashboard-443] 10.1.0.60:8443 87 0.050 200 476f979dc01714dd317bdb273f10500a
192.168.65.3 - [192.168.65.3] - - [30/Apr/2019:04:46:41 +0000] "POST /api/v1/login HTTP/1.1" 200 1467 "http://dashboard.etby.studio/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36" 1479 0.013 [kube-system-dashboard-kubernetes-dashboard-443] 10.1.0.60:8443 1467 0.020 200 0962eece54870420a8c49e135aa00947
192.168.65.3 - [192.168.65.3] - - [30/Apr/2019:04:46:41 +0000] "GET /api/v1/login/status HTTP/1.1" 200 93 "http://dashboard.etby.studio/" "Mozilla/5.0 (Macintosh; Intel Mac OS X 10_14_4) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/73.0.3683.103 Safari/537.36" 403 0.071 [kube-system-dashboard-kubernetes-dashboard-443] 10.1.0.60:8443 93 0.070 200 d0d1fbcf95a331b55c8f74e7466b6f8f

dashboard log

2019/04/30 04:45:44 [2019-04-30T04:45:44Z] Incoming HTTP/1.1 GET /api/v1/settings/global request from 10.1.0.57:43692: {}
2019/04/30 04:45:44 MSG_LOGIN_UNAUTHORIZED_ERROR
2019/04/30 04:45:44 [2019-04-30T04:45:44Z] Outcoming response to 10.1.0.57:43692 with 401 status code
2019/04/30 04:45:44 [2019-04-30T04:45:44Z] Incoming HTTP/1.1 GET /api/v1/rbac/status request from 10.1.0.57:43692: {}
2019/04/30 04:45:44 MSG_LOGIN_UNAUTHORIZED_ERROR
2019/04/30 04:45:44 [2019-04-30T04:45:44Z] Outcoming response to 10.1.0.57:43692 with 401 status code
2019/04/30 04:45:53 [2019-04-30T04:45:53Z] Incoming HTTP/1.1 GET /api/v1/csrftoken/login request from 10.1.0.57:43692: { contents hidden }
2019/04/30 04:45:53 [2019-04-30T04:45:53Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:45:53 [2019-04-30T04:45:53Z] Incoming HTTP/1.1 POST /api/v1/login request from 10.1.0.57:43692: { contents hidden }
2019/04/30 04:45:53 [2019-04-30T04:45:53Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:45:53 [2019-04-30T04:45:53Z] Incoming HTTP/1.1 GET /api/v1/login/status request from 10.1.0.57:43692: {}
2019/04/30 04:45:53 [2019-04-30T04:45:53Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:45:57 Metric client health check failed: the server could not find the requested resource (get services heapster). Retrying in 30 seconds.
2019/04/30 04:45:59 [2019-04-30T04:45:59Z] Incoming HTTP/1.1 GET /api/v1/csrftoken/login request from 10.1.0.57:43692: { contents hidden }
2019/04/30 04:45:59 [2019-04-30T04:45:59Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:45:59 [2019-04-30T04:45:59Z] Incoming HTTP/1.1 POST /api/v1/login request from 10.1.0.57:43692: { contents hidden }
2019/04/30 04:45:59 [2019-04-30T04:45:59Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:45:59 [2019-04-30T04:45:59Z] Incoming HTTP/1.1 GET /api/v1/login/status request from 10.1.0.57:43692: {}
2019/04/30 04:45:59 [2019-04-30T04:45:59Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:45:59 [2019-04-30T04:45:59Z] Incoming HTTP/1.1 GET /api/v1/csrftoken/login request from 10.1.0.57:43692: { contents hidden }
2019/04/30 04:45:59 [2019-04-30T04:45:59Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:45:59 [2019-04-30T04:45:59Z] Incoming HTTP/1.1 POST /api/v1/login request from 10.1.0.57:43692: { contents hidden }
2019/04/30 04:45:59 [2019-04-30T04:45:59Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:45:59 [2019-04-30T04:45:59Z] Incoming HTTP/1.1 GET /api/v1/login/status request from 10.1.0.57:43692: {}
2019/04/30 04:45:59 [2019-04-30T04:45:59Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:45:59 [2019-04-30T04:45:59Z] Incoming HTTP/1.1 GET /api/v1/csrftoken/login request from 10.1.0.57:43692: { contents hidden }
2019/04/30 04:45:59 [2019-04-30T04:45:59Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:45:59 [2019-04-30T04:45:59Z] Incoming HTTP/1.1 POST /api/v1/login request from 10.1.0.57:43692: { contents hidden }
2019/04/30 04:45:59 [2019-04-30T04:45:59Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:45:59 [2019-04-30T04:45:59Z] Incoming HTTP/1.1 GET /api/v1/login/status request from 10.1.0.57:43692: {}
2019/04/30 04:45:59 [2019-04-30T04:45:59Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:45:59 [2019-04-30T04:45:59Z] Incoming HTTP/1.1 GET /api/v1/csrftoken/login request from 10.1.0.57:43692: { contents hidden }
2019/04/30 04:45:59 [2019-04-30T04:45:59Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:45:59 [2019-04-30T04:45:59Z] Incoming HTTP/1.1 POST /api/v1/login request from 10.1.0.57:43692: { contents hidden }
2019/04/30 04:45:59 [2019-04-30T04:45:59Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:45:59 [2019-04-30T04:45:59Z] Incoming HTTP/1.1 GET /api/v1/login/status request from 10.1.0.57:43692: {}
2019/04/30 04:45:59 [2019-04-30T04:45:59Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:46:00 [2019-04-30T04:46:00Z] Incoming HTTP/1.1 GET /api/v1/csrftoken/login request from 10.1.0.57:43692: { contents hidden }
2019/04/30 04:46:00 [2019-04-30T04:46:00Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:46:00 [2019-04-30T04:46:00Z] Incoming HTTP/1.1 POST /api/v1/login request from 10.1.0.57:43692: { contents hidden }
2019/04/30 04:46:00 [2019-04-30T04:46:00Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:46:00 [2019-04-30T04:46:00Z] Incoming HTTP/1.1 GET /api/v1/login/status request from 10.1.0.57:43692: {}
2019/04/30 04:46:00 [2019-04-30T04:46:00Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:46:00 [2019-04-30T04:46:00Z] Incoming HTTP/1.1 GET /api/v1/csrftoken/login request from 10.1.0.57:43692: { contents hidden }
2019/04/30 04:46:00 [2019-04-30T04:46:00Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:46:00 [2019-04-30T04:46:00Z] Incoming HTTP/1.1 POST /api/v1/login request from 10.1.0.57:43692: { contents hidden }
2019/04/30 04:46:00 [2019-04-30T04:46:00Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:46:00 [2019-04-30T04:46:00Z] Incoming HTTP/1.1 GET /api/v1/login/status request from 10.1.0.57:43692: {}
2019/04/30 04:46:00 [2019-04-30T04:46:00Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:46:00 [2019-04-30T04:46:00Z] Incoming HTTP/1.1 GET /api/v1/csrftoken/login request from 10.1.0.57:43692: { contents hidden }
2019/04/30 04:46:00 [2019-04-30T04:46:00Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:46:00 [2019-04-30T04:46:00Z] Incoming HTTP/1.1 POST /api/v1/login request from 10.1.0.57:43692: { contents hidden }
2019/04/30 04:46:00 [2019-04-30T04:46:00Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:46:00 [2019-04-30T04:46:00Z] Incoming HTTP/1.1 GET /api/v1/login/status request from 10.1.0.57:43692: {}
2019/04/30 04:46:00 [2019-04-30T04:46:00Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:46:00 [2019-04-30T04:46:00Z] Incoming HTTP/1.1 GET /api/v1/csrftoken/login request from 10.1.0.57:43692: { contents hidden }
2019/04/30 04:46:00 [2019-04-30T04:46:00Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:46:00 [2019-04-30T04:46:00Z] Incoming HTTP/1.1 POST /api/v1/login request from 10.1.0.57:43692: { contents hidden }
2019/04/30 04:46:00 [2019-04-30T04:46:00Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:46:00 [2019-04-30T04:46:00Z] Incoming HTTP/1.1 GET /api/v1/login/status request from 10.1.0.57:43692: {}
2019/04/30 04:46:00 [2019-04-30T04:46:00Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:46:27 Metric client health check failed: the server could not find the requested resource (get services heapster). Retrying in 30 seconds.
2019/04/30 04:46:41 [2019-04-30T04:46:41Z] Incoming HTTP/1.1 GET /api/v1/csrftoken/login request from 10.1.0.57:43692: { contents hidden }
2019/04/30 04:46:41 [2019-04-30T04:46:41Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:46:41 [2019-04-30T04:46:41Z] Incoming HTTP/1.1 POST /api/v1/login request from 10.1.0.57:43692: { contents hidden }
2019/04/30 04:46:41 [2019-04-30T04:46:41Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:46:41 [2019-04-30T04:46:41Z] Incoming HTTP/1.1 GET /api/v1/login/status request from 10.1.0.57:43692: {}
2019/04/30 04:46:41 [2019-04-30T04:46:41Z] Outcoming response to 10.1.0.57:43692 with 200 status code
2019/04/30 04:46:57 Metric client health check failed: the server could not find the requested resource (get services heapster). Retrying in 30 seconds.
2019/04/30 04:47:27 Metric client health check failed: the server could not find the requested resource (get services heapster). Retrying in 30 seconds.
2019/04/30 04:47:57 Metric client health check failed: the server could not find the requested resource (get services heapster). Retrying in 30 seconds.
2019/04/30 04:48:27 Metric client health check failed: the server could not find the requested resource (get services heapster). Retrying in 30 seconds.
2019/04/30 04:48:57 Metric client health check failed: the server could not find the requested resource (get services heapster). Retrying in 30 seconds.
2019/04/30 04:49:27 Metric client health check failed: the server could not find the requested resource (get services heapster). Retrying in 30 seconds.
2019/04/30 04:49:57 Metric client health check failed: the server could not find the requested resource (get services heapster). Retrying in 30 seconds.
lifecyclstale
Source
picture etby

Most helpful comment

I do have the same issue. Any updates on this? How can this be solved? Clicking on "Login" just does nothing.

picture hansingt on 29 Jul 2019
👍6

All 4 comments

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Any further update will cause the issue/pull request to no longer be considered stale. Thank you for your contributions.

stale[bot] picture stale[bot] on 30 May 2019

This issue is being automatically closed due to inactivity.

stale[bot] picture stale[bot] on 13 Jun 2019

I do have the same issue. Any updates on this? How can this be solved? Clicking on "Login" just does nothing.

hansingt picture hansingt on 29 Jul 2019
👍6

In case somebody have a similar problem and arrives on that closed issue: the solution is to use https instead of http in your broser.

open https://kubernetes-dashboard.domain.com

jderusse picture jderusse on 5 Feb 2020
Was this page helpful?
0 / 5 - 0 ratings

Related issues

mluedke picture mluedke  路  3Comments
paskal picture paskal  路  3Comments
ChrisCooney picture ChrisCooney  路  3Comments
michas2 picture michas2  路  3Comments
jungopro picture jungopro  路  3Comments