Kubernetes-基于k8s-v1.14.2安装dashboard-1.10.1
上篇文章中,已经完成了基于kubeadm安装的kubernetes集群,本文将基于上述的集群环境,搭建dashboard组件。
安装环境及版本
kubernetes版本及基础组件版本可参考前一篇安装集群环境的文章
dashboard组件:kubernetes-dashboard-v1.10.1
需准备的镜像:
k8s.gcr.io/kubernetes-dashboard-amd64:v1.10.1
k8s.gcr.io/heapster-amd64:v1.5.4
k8s.gcr.io/heapster-influxdb-amd64:v1.5.2
k8s.gcr.io/heapster-grafana-amd64:v5.0.4
#!/bin/bash DASHDOARD_VERSION=v1.10.1 HEAPSTER_VERSION=v1.5.4 GRAFANA_VERSION=v5.0.4 INFLUXDB_VERSION=v1.5.2 username=registry.cn-hangzhou.aliyuncs.com/google_containers images=(kubernetes-dashboard-amd64:${DASHDOARD_VERSION}heapster-grafana-amd64:${GRAFANA_VERSION}heapster-amd64:${HEAPSTER_VERSION}heapster-influxdb-amd64:${INFLUXDB_VERSION}) for image in ${images[@]} do docker pull ${username}/${image} docker tag ${username}/${image} k8s.gcr.io/${image} docker rmi ${username}/${image} done
主节点与个node节点均需要以上镜像:
k8s.gcr.io/kubernetes-dashboard-amd64 v1.10.1 f9aed6605b81 3 months ago 122MB k8s.gcr.io/heapster-amd64 v1.5.4 72d68eecf40c 8 months ago 75.3MB k8s.gcr.io/heapster-influxdb-amd64 v1.5.2 eb180058aee0 8 months ago 16.5MB k8s.gcr.io/heapster-grafana-amd64 v5.0.4 25e1da333f76 8 months ago 171MB
在主节点上准备部署所需的yaml文件:
dashboard项目官方地址:https://github.com/kubernetes/dashboard/releases
这是作者自己修改过的yaml文件: https://github.com/chopperchan/k8s-dashboard.git
包含有:
kubernetes-dashboard.yaml
# Copyright 2017 The Kubernetes Authors. # # Licensed under the Apache License, Version 2.0 (the "License"); # you may not use this file except in compliance with the License. # You may obtain a copy of the License at # # http://www.apache.org/licenses/LICENSE-2.0 # # Unless required by applicable law or agreed to in writing, software # distributed under the License is distributed on an "AS IS" BASIS, # WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. # See the License for the specific language governing permissions and # limitations under the License.# Configuration to deploy release version of the Dashboard UI compatible with # Kubernetes 1.8. # # Example usage: kubectl create -f <this_file># ------------------- Dashboard Secret ------------------- #apiVersion: v1 kind: Secret metadata:labels:k8s-app: kubernetes-dashboardname: kubernetes-dashboard-certsnamespace: kube-system type: Opaque--- # ------------------- Dashboard Service Account ------------------- #apiVersion: v1 kind: ServiceAccount metadata:labels:k8s-app: kubernetes-dashboardname: kubernetes-dashboardnamespace: kube-system--- # ------------------- Dashboard Role & Role Binding ------------------- #kind: Role apiVersion: rbac.authorization.k8s.io/v1 metadata:name: kubernetes-dashboard-minimalnamespace: kube-system rules:# Allow Dashboard to create 'kubernetes-dashboard-key-holder' secret. - apiGroups: [""]resources: ["secrets"]verbs: ["create"]# Allow Dashboard to create 'kubernetes-dashboard-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-dashboard-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-minimalnamespace: kube-system roleRef:apiGroup: rbac.authorization.k8s.iokind: Rolename: kubernetes-dashboard-minimal subjects: - kind: ServiceAccountname: kubernetes-dashboardnamespace: kube-system--- # ------------------- Dashboard Deployment ------------------- #kind: Deployment apiVersion: apps/v1beta2 metadata:labels:k8s-app: kubernetes-dashboardname: kubernetes-dashboardnamespace: kube-system spec:replicas: 1revisionHistoryLimit: 10selector:matchLabels:k8s-app: kubernetes-dashboardtemplate:metadata:labels:k8s-app: kubernetes-dashboardspec:containers:- name: kubernetes-dashboardimage: k8s.gcr.io/kubernetes-dashboard-amd64:v1.10.1ports:- containerPort: 9090protocol: TCPargs:#- --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://10.0.1.168:8080 volumeMounts:- name: kubernetes-dashboard-certsmountPath: /certs# Create on-disk volume to store exec logs- mountPath: /tmpname: tmp-volumelivenessProbe:httpGet:scheme: HTTPpath: /port: 9090initialDelaySeconds: 30timeoutSeconds: 30volumes:- name: kubernetes-dashboard-certssecret:secretName: kubernetes-dashboard-certs- name: tmp-volumeemptyDir: {}serviceAccountName: kubernetes-dashboard-admin# Comment the following tolerations if Dashboard must not be deployed on mastertolerations:- key: node-role.kubernetes.io/mastereffect: NoSchedule--- # ------------------- Dashboard Service ------------------- #kind: Service apiVersion: v1 metadata:labels:k8s-app: kubernetes-dashboardname: kubernetes-dashboardnamespace: kube-system spec:ports:- port: 9090targetPort: 9090selector:k8s-app: kubernetes-dashboard# ------------------------------------------------------------ kind: Service apiVersion: v1 metadata:labels:k8s-app: kubernetes-dashboardname: kubernetes-dashboard-externalnamespace: kube-system spec:ports:- port: 9090targetPort: 9090nodePort: 31666type: NodePortselector:k8s-app: kubernetes-dashboard
kubernetes-dashboard-admin.rbac.yaml
--- apiVersion: v1 kind: ServiceAccount metadata:labels:k8s-app: kubernetes-dashboardname: kubernetes-dashboard-adminnamespace: kube-system--- apiVersion: rbac.authorization.k8s.io/v1beta1 kind: ClusterRoleBinding metadata:name: kubernetes-dashboard-adminlabels:k8s-app: kubernetes-dashboard roleRef:apiGroup: rbac.authorization.k8s.iokind: ClusterRolename: cluster-admin subjects: - kind: ServiceAccountname: kubernetes-dashboard-adminnamespace: kube-system
heapster.yaml
apiVersion: v1 kind: ServiceAccount metadata:name: heapsternamespace: kube-system --- apiVersion: extensions/v1beta1 kind: Deployment metadata:name: heapsternamespace: kube-system spec:replicas: 1template:metadata:labels:task: monitoringk8s-app: heapsterspec:serviceAccountName: heapstercontainers:- name: heapsterimage: k8s.gcr.io/heapster-amd64:v1.5.4imagePullPolicy: IfNotPresentcommand:- /heapster- --source=kubernetes:https://kubernetes.default- --sink=influxdb:http://monitoring-influxdb.kube-system.svc:8086 --- apiVersion: v1 kind: Service metadata:labels:task: monitoring# For use as a Cluster add-on (https://github.com/kubernetes/kubernetes/tree/master/cluster/addons)# If you are NOT using this as an addon, you should comment out this line.kubernetes.io/cluster-service: 'true'kubernetes.io/name: Heapstername: heapsternamespace: kube-system spec:ports:- port: 80targetPort: 8082selector:k8s-app: heapster
heapster-rbac.yaml
kind: ClusterRoleBinding apiVersion: rbac.authorization.k8s.io/v1beta1 metadata:name: heapster roleRef:apiGroup: rbac.authorization.k8s.iokind: ClusterRolename: system:heapster subjects: - kind: ServiceAccountname: heapsternamespace: kube-system
官方的文件中只包含了kubernetes-dashboard.yaml,且kubernetes在1.6版本以后启用了RBAC访问控制策略,直接使用官方版会出现访问权限不足的报错
此问题可使用kubectl或Kubernetes API进行配置。使用RBAC可以直接授权给用户,让用户拥有授权管理的权限,这样就不再需要直接触碰Master Node。
相关修改为:
kubernetes-dashboard.yaml 中修改 serviceAccountName,外部访问dashboard的方式(本文为token访问)
kubernetes-dashboard-admin(默认为kubernetes-dashboard)
kind: Service apiVersion: v1 metadata:labels:k8s-app: kubernetes-dashboardname: kubernetes-dashboard-externalnamespace: kube-system spec:ports:- port: 9090targetPort: 9090nodePort: 31666type: NodePortselector:k8s-app: kubernetes-dashboard
在kubernetes-dashboard-admin.rbac.yaml中则是执行了创建kubernetes-dashboard-admin用户并赋予所有权限的命令
PS:yaml中涉及的image版本请根据自己实际情况调整
安装dashboard及相关组件
ll #以下内容其中grafana和influxdb是作者自己增加的,读者可不用部署 -rw-r--r-- 1 root root 2314 4月 3 10:02 grafana.yaml -rw-r--r-- 1 root root 264 11月 23 15:19 heapster-rbac.yaml -rw-r--r-- 1 root root 1100 4月 3 09:52 heapster.yaml -rw-r--r-- 1 root root 998 4月 3 10:02 influxdb.yaml -rw-r--r-- 1 root root 504 4月 3 10:13 kubernetes-dashboard-admin.rbac.yaml -rw-r--r-- 1 root root 5132 4月 3 12:40 kubernetes-dashboard.yaml#执行安装 kubectl apply -n kube-system -f .#执行完成后查看pod是否正常运行 kubectl get pod -n kube-system |grep kubernetes-dashboardkubernetes-dashboard-6cfdc589c7-krfmk 1/1 Running 0 164m#查看服务暴露的端口号 kubectl get service -n kube-system |grep kubernetes-dashboard kubernetes-dashboard-external NodePort 10.98.178.105 <none> 9090:31666/TCP 168m
Running状态说明运行正常,直接可通过masterip:端口号访问ui界面。
读者可根据需要修改nodePort参数来修改访问端口。
可能会遇到的问题
访问时出现权限不足
解决方法:
执行本文中的kubernetes-dashboard-admin.rbac.yaml,或读者自行创建serviceAccount,并修改kubernetes-dashboard.yml中serviceAccount参数为你创建的用户名称
转载于:https://www.cnblogs.com/ling-yu-amen/p/10955094.html
Kubernetes-基于k8s-v1.14.2安装dashboard-1.10.1相关推荐
- Kubernetes(K8s)集群安装部署
Kubernetes(K8s)集群安装 Kubernetes(K8s)集群安装 1 .基本环境配置 1.1.Kubernetes集群规划 1.2.基础环境配置(所有节点) 1.2.1.Host文件修改 ...
- centos7 下google Kubernetes(k8s)集群安装部署
centos7 下google Kubernetes(k8s)集群安装部署 简介 安装环境 安装前准备 ECTD集群配置 命令含义: master节点配置 1.安装kubernetes和etcd 2. ...
- Kubernetes1.13集群安装dashboard 1.10.1
文章目录 Kubernetes1.13集群安装dashboard 1.10.1 安装dashboard 下载镜像 创建pod 授予Dashboard账户集群管理权限 APIServer方式 查看集群信 ...
- 【K8S】K8S 1.18.2安装dashboard(基于kubernetes-dashboard 2.0.0版本)
写在前面 K8S集群部署成功了,如何对集群进行可视化管理呢?别着急,接下来,我们一起搭建kubernetes-dashboard来解决这个问题. 有关K8S集群的安装可以参考<[K8S]基于单M ...
- kubernetes【k8s】adm方式安装[超级详细]
集群规划[1master节点2node节点] 主机名 IP地址 推荐配置 k8s-master 172.16.115.237 1C2G40G k8s-node1 172.16.115.238 1C2G ...
- sealos kubernetes(k8s)高可用安装教程
官网地址 https://www.sealyun.com/instructions 快速开始 环境信息 主机名 IP地址 master0 192.168.0.2 master1 192.168.0.3 ...
- 【kubernetes】k8s v1.20高可用多master节点部署
一,安装环境 1,硬件要求 内存:2GB或更多RAM CPU: 2核CPU或更多CPU 硬盘: 30GB或更多 2,本次环境说明: 操作系统:CentOS 7.9 内核版本:3.10.0-1160 虚 ...
- Prometheus 基于k8s服务发现通过Cadvisor监控Kubernetes
Prometheus服务发现 Prometheus添加被监控端支持两种方式: • 静态配置:手动配置 • 服务发现:动态发现需要监控的Target实例 支持服务发现的来源 • azure_sd_con ...
- 关于 Kubernetes集群中仪表盘(dashboardKuboard)安装的一些笔记
写在前面 学习K8s,整理记忆 博文内容涉及 K8s面板工具dashboard和Kuboard. dashboard以及Kuboard部署Demo 部分地方使用了Ansible,只用了shell,co ...
- Kubernetes 生产环境安装部署 基于 Kubernetes v1.14.0 之 etcd集群
说明:没有明确注明在某台服务器,都是在k8s-operation 工作服务器完成 K8S node 节点数大于2000 节点 k8s-operation 目录规划,工作目录/apps/work/k8s ...
最新文章
- 影像组学视频学习笔记(21)-影像组学常用软件推荐、Li‘s have a solution and plan.
- 不确定大小的数组_原来数组是容器喔
- [OS复习]进程管理2
- python实现dns劫持_Python程序之DNS劫持
- git 分支复制_Git基础知识(五)
- iOS 文件预览 UIDocumentInteractionController
- CodeForces730E Award Ceremony(拓扑排序+结论)
- Java英雄:丹·艾伦
- dataframe第二列 r语言_123.R简介和统计绘图
- chrome浏览器功能介绍
- socket通信基础知识
- Spring Boot 消息
- Win8 内置游戏应用更新 中文翻译错误得以修正
- 从php的生命周期来优化页面响应时间
- 加密Python源代码笔记
- 中兴B860 AV2.1 S905L刷入armbian并启用docker且使用Portainer汉化版控制面板
- WAP常见问题问答大全
- ThinkPHP带表情无限级评论回复
- 服务器装系统步骤图解win7,win7安装系统图解教程
- [创业之路-50] :动态股权机制 -5- 创业公司股权分配常见的坑