Kubernetes Dashboard 設置用戶密碼登陸
Kubernetes
2019年05月20日
K8s 文檔
K8s 1.13源碼安裝
k8s dashboard token訪問
儀表板是基於Web的Kubernetes用戶界面。您可以使用儀表板將容器化應用程序部署到Kubernetes集羣,對容器化應用程序進行故障排除,並管理集羣本身及其伴隨資源。您可以使用儀表板來概述羣集上運行的應用程序,以及創建或修改單個Kubernetes資源(例如部署,作業,守護進程等)。例如,您可以使用部署嚮導擴展部署,啓動滾動更新,重新啓動Pod或部署新應用程序。
默認Kubernetes UI界面是使用token登陸,但是由於token相比較麻煩。我們這裏使用密碼登陸
1.首先確保K8S集羣內部一切正常
[root@i4t ~]# kubectl get node
NAME STATUS ROLES AGE VERSION
yzsjhl82-138.opi.com Ready <none> 22h v1.13.5
yzsjhl82-139.opi.com Ready <none> 22h v1.13.5
yzsjhl82-140.opi.com Ready <none> 22h v1.13.5
yzsjhl82-142.opi.com Ready <none> 22h v1.13.5
[root@i4t ~]# kubectl get pod --all-namespaces
NAMESPACE NAME READY STATUS RESTARTS AGE
default busybox 1/1 Running 23 22h
kube-system coredns-d7964c8db-2t8wl 1/1 Running 1 22h
kube-system coredns-d7964c8db-sbztp 1/1 Running 1 22h
kube-system kube-flannel-ds-amd64-cv5hx 1/1 Running 2 22h
kube-system kube-flannel-ds-amd64-f2f7x 1/1 Running 2 22h
kube-system kube-flannel-ds-amd64-vmm74 1/1 Running 2 22h
kube-system kube-flannel-ds-amd64-zgfmq 1/1 Running 1 22h
2.配置
首先需要說明一點,默認kubernetes Dashboard是需要token登陸。不方便登記,我們可以讓dashboard使用用戶密碼驗證登陸
需要注意幾點
- 修改apiserver
- 創建用戶密碼文件
- 創建yaml文件
[一] 在master上節點上創建文件(用戶密碼文件)
cat /etc/kubernetes/basic_auth_file
admin,admin,1
cyh,cyh,2
#前面爲用戶,後面爲密碼,數字爲用戶ID不可重複
[二] 在所有master的apiserver啓動文件添加一行配置
vim /usr/lib/systemd/system/kube-apiserver.service
--basic-auth-file=/etc/kubernetes/basic_auth_file \
#添加完畢後重啓api-server
這裏需要說明,以上操作在所有master上執行,在所有節點操作是爲了防止有pod飄到非master節點,當然也可以做pod親和力
[三]創建yaml文件
wget http://down.i4t.com/k8s-passwd-dashboard.yaml| kubectl apply -f k8s-passwd-dashboard.yaml
爲了防止地址失效,我這裏在手動cp一份
# ------------------- Dashboard Secret ------------------- #
apiVersion: v1
kind: Secret
metadata:
labels:
k8s-app: kubernetes-dashboard
name: kubernetes-dashboard-certs
namespace: kube-system
type: Opaque
---
# ------------------- Dashboard Service Account ------------------- #
apiVersion: v1
kind: ServiceAccount
metadata:
labels:
k8s-app: kubernetes-dashboard
name: kubernetes-dashboard
namespace: kube-system
---
# ------------------- Dashboard Role & Role Binding ------------------- #
kind: Role
apiVersion: rbac.authorization.k8s.io/v1
metadata:
name: kubernetes-dashboard-minimal
namespace: kube-system
rules:
# Allow Dashboard to create 'kubernetes-dashboard2-key-holder' secret.
- apiGroups: [""]
resources: ["secrets"]
verbs: ["create"]
# Allow Dashboard to create 'kubernetes-dashboard2-settings' config map.
- apiGroups: [""]
resources: ["configmaps"]
verbs: ["create"]
# Allow Dashboard to get, update and delete Dashboard exclusive secrets.
- apiGroups: [""]
resources: ["secrets"]
resourceNames: ["kubernetes-dashboard-key-holder", "kubernetes-dashboard-certs"]
verbs: ["get", "update", "delete"]
# Allow Dashboard to get and update 'kubernetes-dashboard2-settings' config map.
- apiGroups: [""]
resources: ["configmaps"]
resourceNames: ["kubernetes-dashboard-settings"]
verbs: ["get", "update"]
# Allow Dashboard to get metrics from heapster.
- apiGroups: [""]
resources: ["services"]
resourceNames: ["heapster"]
verbs: ["proxy"]
- apiGroups: [""]
resources: ["services/proxy"]
resourceNames: ["heapster", "http:heapster:", "https:heapster:"]
verbs: ["get"]
---
apiVersion: rbac.authorization.k8s.io/v1
kind: RoleBinding
metadata:
name: kubernetes-dashboard-minimal
namespace: kube-system
roleRef:
apiGroup: rbac.authorization.k8s.io
kind: Role
name: kubernetes-dashboard-minimal
subjects:
- kind: ServiceAccount
name: kubernetes-dashboard
namespace: kube-system
---
# ------------------- Dashboard Deployment ------------------- #
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: mirrorgooglecontainers/kubernetes-dashboard-amd64:v1.8.3
ports:
- containerPort: 8443
protocol: TCP
args:
- --auto-generate-certificates
- --authentication-mode=basic
# 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
---
# ------------------- Dashboard Service ------------------- #
kind: Service
apiVersion: v1
metadata:
labels:
k8s-app: kubernetes-dashboard
name: kubernetes-dashboard
namespace: kube-system
spec:
type: NodePort
ports:
- port: 80
targetPort: 8443
nodePort: 30000
selector:
k8s-app: kubernetes-dashboard
我們可以用過下面命令進行檢查
kubectl get pod,svc -n kube-system
這裏要說一點,我這裏的鏡像使用的是v1.8.3
如果覺得版本低可以更高版本的。
訪問dashboard界面
由於沒有ingress,使用的是IP訪問。所以會提示我們證書不安全,我們這裏點擊忽略直接訪問。個別瀏覽器會造成打不開的,建議使用谷歌或火狐
在任意一臺master上訪問即可
這裏需要我們輸入api-server指定的文件裏面的賬號密碼
跳過是沒有權限查看k8s裏面所有的信息