09-2.部署 dashboard 插件

注意：如果没有特殊指明，本文档的所有操作均在 m7-autocv-gpu01 节点上执行。

修改配置文件

将下载的 kubernetes-server-linux-amd64.tar.gz 解压后，再解压其中的 kubernetes-src.tar.gz 文件。

dashboard 对应的目录是：cluster/addons/dashboard。

  1. cd /opt/k8s/work/kubernetes/cluster/addons/dashboard
  1. $ cat dashboard-service.yaml
  2. apiVersion: v1
  3. kind: Service
  4. metadata:
  5.   name: kubernetes-dashboard
  6.   namespace: kube-system
  7.   labels:
  8.     k8s-app: kubernetes-dashboard
  9.     kubernetes.io/cluster-service: "true"
  10.     addonmanager.kubernetes.io/mode: Reconcile
  11. spec:
  12.   type: NodePort # 增加这一行
  13.   selector:
  14.     k8s-app: kubernetes-dashboard
  15.   ports:
  16.   - port: 443
  17.     targetPort: 8443
  • 指定端口类型为 NodePort，这样外界可以通过地址 nodeIP:nodePort 访问 dashboard；

执行所有定义文件

  1. $ ls *.yaml
  2. dashboard-configmap.yaml  dashboard-controller.yaml  dashboard-rbac.yaml  dashboard-secret.yaml  dashboard-service.yaml
  4. $ kubectl create -f  .

查看分配的 NodePort

  1. $ kubectl get deployment kubernetes-dashboard  -n kube-system
  2. NAME                   DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
  3. kubernetes-dashboard   1         1         1            1           2m
  5. $ kubectl --namespace kube-system get pods -o wide
  6. NAME                                    READY     STATUS    RESTARTS   AGE       IP             NODE              NOMINATED NODE
  7. coredns-77cd44d8df-4fmfc                1/1       Running   0          1h        172.30.200.2   m7-autocv-gpu03   <none>
  8. kubernetes-dashboard-69db8c7745-jtvpj   1/1       Running   0          55s       172.30.112.3   m7-autocv-gpu01   <none>
  10. $ kubectl get services kubernetes-dashboard -n kube-system
  11. NAME                   TYPE       CLUSTER-IP     EXTERNAL-IP   PORT(S)         AGE
  12. kubernetes-dashboard   NodePort   10.254.9.198   <none>        443:32014/TCP   1m
  • NodePort 32014 映射到 dashboard pod 443 端口；

dashboard 的 —authentication-mode 支持 token、basic，默认为 token。如果使用 basic，则 kube-apiserver 必须配置 ‘—authorization-mode=ABAC’ 和 ‘—basic-auth-file’ 参数。

查看 dashboard 支持的命令行参数

  1. $ kubectl exec --namespace kube-system -it kubernetes-dashboard-69db8c7745-jtvpj  -- /dashboard --help # kubernetes-dashboard-69db8c7745-jtvpj 为 pod 名称
  2. 2018/08/15 13:12:03 Starting overwatch
  3. Usage of /dashboard:
  4.       --alsologtostderr                   log to standard error as well as files
  5.       --apiserver-host string             The address of the Kubernetes Apiserver to connect to in the format of protocol://address:port, e.g., http://localhost:8080. If not specified, the assumption is that the binary runs inside a Kubernetes cluster and local discovery is attempted.
  6.       --authentication-mode stringSlice   Enables authentication options that will be reflected on login screen. Supported values: token, basic. Default: token.Note that basic option should only be used if apiserver has '--authorization-mode=ABAC' and '--basic-auth-file' flags set. (default [token])
  7.       --auto-generate-certificates        When set to true, Dashboard will automatically generate certificates used to serve HTTPS. Default: false.
  8.       --bind-address ip                   The IP address on which to serve the --secure-port (set to 0.0.0.0 for all interfaces). (default 0.0.0.0)
  9.       --default-cert-dir string           Directory path containing '--tls-cert-file' and '--tls-key-file' files. Used also when auto-generating certificates flag is set. (default "/certs")
  10.       --disable-settings-authorizer       When enabled, Dashboard settings page will not require user to be logged in and authorized to access settings page.
  11.       --enable-insecure-login             When enabled, Dashboard login view will also be shown when Dashboard is not served over HTTPS. Default: false.
  12.       --heapster-host string              The address of the Heapster Apiserver to connect to in the format of protocol://address:port, e.g., http://localhost:8082. If not specified, the assumption is that the binary runs inside a Kubernetes cluster and service proxy will be used.
  13.       --insecure-bind-address ip          The IP address on which to serve the --port (set to 0.0.0.0 for all interfaces). (default 127.0.0.1)
  14.       --insecure-port int                 The port to listen to for incoming HTTP requests. (default 9090)
  15.       --kubeconfig string                 Path to kubeconfig file with authorization and master location information.
  16.       --log_backtrace_at traceLocation    when logging hits line file:N, emit a stack trace (default :0)
  17.       --log_dir string                    If non-empty, write log files in this directory
  18.       --logtostderr                       log to standard error instead of files
  19.       --metric-client-check-period int    Time in seconds that defines how often configured metric client health check should be run. Default: 30 seconds. (default 30)
  20.       --port int                          The secure port to listen to for incoming HTTPS requests. (default 8443)
  21.       --stderrthreshold severity          logs at or above this threshold go to stderr (default 2)
  22.       --system-banner string              When non-empty displays message to Dashboard users. Accepts simple HTML tags. Default: ''.
  23.       --system-banner-severity string     Severity of system banner. Should be one of 'INFO|WARNING|ERROR'. Default: 'INFO'. (default "INFO")
  24.       --tls-cert-file string              File containing the default x509 Certificate for HTTPS.
  25.       --tls-key-file string               File containing the default x509 private key matching --tls-cert-file.
  26.       --token-ttl int                     Expiration time (in seconds) of JWE tokens generated by dashboard. Default: 15 min. 0 - never expires (default 900)
  27.   -v, --v Level                           log level for V logs
  28.       --vmodule moduleSpec                comma-separated list of pattern=N settings for file-filtered logging
  29. command terminated with exit code 2

访问 dashboard

为了集群安全，从 1.7 开始，dashboard 只允许通过 https 访问，如果使用 kube proxy 则必须监听 localhost 或 127.0.0.1，对于 NodePort 没有这个限制，但是仅建议在开发环境中使用。

对于不满足这些条件的登录访问，在登录成功后浏览器不跳转，始终停在登录界面。

参考： https://github.com/kubernetes/dashboard/wiki/Accessing-Dashboard---1.7.X-and-above https://github.com/kubernetes/dashboard/issues/2540

  1. kubernetes-dashboard 服务暴露了 NodePort，可以使用 https://NodeIP:NodePort 地址访问 dashboard；
  2. 通过 kube-apiserver 访问 dashboard；
  3. 通过 kubectl proxy 访问 dashboard：

如果使用了 VirtualBox，需要启用 VirtualBox 的 ForworadPort 功能将虚机监听的端口和 Host 的本地端口绑定。

可以在 Vagrant 的配置中指定这些端口转发规则，对于正在运行的虚机，也可以通过 VirtualBox 的界面进行配置：

virtualbox-1 virtualbox-2

通过 kubectl proxy 访问 dashboard

启动代理：

  1. $ kubectl proxy --address='localhost' --port=8086 --accept-hosts='^*$'
  2. Starting to serve on 127.0.0.1:8086
  • —address 必须为 localhost 或 127.0.0.1；
  • 需要指定 --accept-hosts 选项，否则浏览器访问 dashboard 页面时提示 “Unauthorized”；

浏览器访问 URL：http://127.0.0.1:8086/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy

通过 kube-apiserver 访问 dashboard

获取集群服务地址列表：

  1. $ kubectl cluster-info
  2. Kubernetes master is running at https://127.0.0.1:8443
  3. CoreDNS is running at https://127.0.0.1:8443/api/v1/namespaces/kube-system/services/kube-dns:dns/proxy
  4. kubernetes-dashboard is running at https://127.0.0.1:8443/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy
  6. To further debug and diagnose cluster problems, use 'kubectl cluster-info dump'.
  • 由于 apiserver 通过本地的 kube-nginx 做了代理，所以上面显示的 127.0.0.1:8443 为本地的 kube-nginx 的 IP 和 Port，浏览器访问时需要替换为 kube-apiserver 实际监听的 IP 和端口，如 172.27.128.149:6443；
  • 必须通过 kube-apiserver 的安全端口(https)访问 dashbaord，访问时浏览器需要使用自定义证书，否则会被 kube-apiserver 拒绝访问。
  • 创建和导入自定义证书的步骤，参考：A.浏览器访问kube-apiserver安全端口

浏览器访问 URL：https://172.27.128.149:6443/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy 对于 virtuabox 做了端口映射： http://127.0.0.1:6443/api/v1/namespaces/kube-system/services/https:kubernetes-dashboard:/proxy/

dashboard-login

创建登录 Dashboard 的 token 和 kubeconfig 配置文件

上面提到，Dashboard 默认只支持 token 认证，所以如果使用 KubeConfig 文件，需要在该文件中指定 token，不支持使用 client 证书认证。

创建登录 token

  1. kubectl create sa dashboard-admin -n kube-system
  2. kubectl create clusterrolebinding dashboard-admin --clusterrole=cluster-admin --serviceaccount=kube-system:dashboard-admin
  3. ADMIN_SECRET=$(kubectl get secrets -n kube-system | grep dashboard-admin | awk '{print $1}')
  4. DASHBOARD_LOGIN_TOKEN=$(kubectl describe secret -n kube-system ${ADMIN_SECRET} | grep -E '^token' | awk '{print $2}')
  5. echo ${DASHBOARD_LOGIN_TOKEN}

使用输出的 token 登录 Dashboard。

创建使用 token 的 KubeConfig 文件

  1. source /opt/k8s/bin/environment.sh
  2. # 设置集群参数
  3. kubectl config set-cluster kubernetes \
  4.   --certificate-authority=/etc/kubernetes/cert/ca.pem \
  5.   --embed-certs=true \
  6.   --server=${KUBE_APISERVER} \
  7.   --kubeconfig=dashboard.kubeconfig
  9. # 设置客户端认证参数，使用上面创建的 Token
  10. kubectl config set-credentials dashboard_user \
  11.   --token=${DASHBOARD_LOGIN_TOKEN} \
  12.   --kubeconfig=dashboard.kubeconfig
  14. # 设置上下文参数
  15. kubectl config set-context default \
  16.   --cluster=kubernetes \
  17.   --user=dashboard_user \
  18.   --kubeconfig=dashboard.kubeconfig
  20. # 设置默认上下文
  21. kubectl config use-context default --kubeconfig=dashboard.kubeconfig

用生成的 dashboard.kubeconfig 登录 Dashboard。

/projects/follow-me-install-kubernetes-cluster-1.12.x/images/dashboard.png

由于缺少 Heapster 插件，当前 dashboard 不能展示 Pod、Nodes 的 CPU、内存等统计数据和图表；

参考

  1. https://github.com/kubernetes/dashboard/wiki/Access-control
  2. https://github.com/kubernetes/dashboard/issues/2558
  3. https://kubernetes.io/docs/concepts/configuration/organize-cluster-access-kubeconfig/