我可以在与目标集群不同的集群上运行 Kubernetes Dashboard答案

【问题标题】：Can I run Kubernetes Dashboard on a separate cluster than the targetted cluster我可以在与目标集群不同的集群上运行 Kubernetes Dashboard
【发布时间】：2018-10-03 03:39:28
【问题描述】：

我已通过代理公开了 Kube API，但我无权在该集群上运行仪表板。我可以在单独的集群上运行仪表板，并将该仪表板指向所需集群的 API 吗？

【问题讨论】：

标签： kubernetes kubernetes-dashboard

【解决方案1】：

是的，你可以。下面是仪表板的首选部署定义（来自仪表板 Github 页面）。您必须取消注释选项 --apiserver-host=http://my-address:port。您还必须确保使用正确的证书和凭据来访问您的 kube-apiserver。出于安全原因，我建议您仅将 kube-apiserver 代理打开到非常特定的主机，例如运行仪表板的主机。

kind: Deployment
apiVersion: apps/v1beta2
metadata:
  labels:
    k8s-app: kubernetes-dashboard
  name: kubernetes-dashboard
  namespace: kube-system
spec:
  replicas: 1
  revisionHistoryLimit: 10
  selector:
    matchLabels:
      k8s-app: kubernetes-dashboard
  template:
    metadata:
      labels:
        k8s-app: kubernetes-dashboard
    spec:
      containers:
      - name: kubernetes-dashboard
        image: k8s.gcr.io/kubernetes-dashboard-amd64:v1.10.0
        ports:
        - containerPort: 8443
          protocol: TCP
        args:
          - --auto-generate-certificates
          # Uncomment the following line to manually specify Kubernetes API server Host
          # If not specified, Dashboard will attempt to auto discover the API server and connect
          # to it. Uncomment only if the default does not work.
          # - --apiserver-host=http://my-address:port
        volumeMounts:
        - name: kubernetes-dashboard-certs
          mountPath: /certs
          # Create on-disk volume to store exec logs
        - mountPath: /tmp
          name: tmp-volume
        livenessProbe:
          httpGet:
            scheme: HTTPS
            path: /
            port: 8443
          initialDelaySeconds: 30
          timeoutSeconds: 30
      volumes:
      - name: kubernetes-dashboard-certs
        secret:
          secretName: kubernetes-dashboard-certs
      - name: tmp-volume
        emptyDir: {}
      serviceAccountName: kubernetes-dashboard
      # Comment the following tolerations if Dashboard must not be deployed on master
      tolerations:
      - key: node-role.kubernetes.io/master
        effect: NoSchedule

【讨论】：