准备Kuboard镜像

#获取Kuboard镜像

• 在可以上网的机器上抓取 kuboard 镜像

  docker pull eipwork/kuboard:latest
  

  已复制到剪贴板！

• 查看 kuboard 镜像的 ID

  docker images | grep kuboard
  

  已复制到剪贴板！

  输出结果如下所示：

  eipwork/kuboard           latest                0146965e6475        3 weeks ago         133MB
  

  已复制到剪贴板！

• 将 Kuboard 镜像导出到文件

  docker save 86eaead8421e > kuboard.tar
  

  已复制到剪贴板！

  ImageID

  请使用上一个步骤中查询到的 image ID

• 将 kuboard.tar 传输到 Kubernetes 集群的某一个节点上

#加载Kuboard镜像

• 在 Kubernetes 集群的某一个节点上执行

  docker load < kuboard.tar
  

  已复制到剪贴板！

• 为镜像重新添加标签

  docker tag 0146965e6475 eipwork/kuboard:latest
  

  已复制到剪贴板！

  ImageID

  请使用上一个步骤中查询到的 image ID

#准备kuboard.yaml文件

安装Kuboard的yaml文件如下，将其保存到 kuboard-offline.yaml

必要的修改

• 修改该文件中第 26 行的节点名称为上一个步骤中，已经加载了 kuboard 镜像的节点，参考 将容器组调度到指定节点

• 与在线安装不同，此处 ImagePullPolicy=IfNotPresent （第30行），参考 容器镜像

apiVersion: apps/v1
kind: Deployment
metadata:
  name: kuboard
  namespace: kube-system
  annotations:
    k8s.kuboard.cn/displayName: kuboard
    k8s.kuboard.cn/ingress: "true"
    k8s.kuboard.cn/service: NodePort
    k8s.kuboard.cn/workload: kuboard
  labels:
    k8s.kuboard.cn/layer: monitor
    k8s.kuboard.cn/name: kuboard
spec:
  replicas: 1
  selector:
    matchLabels:
      k8s.kuboard.cn/layer: monitor
      k8s.kuboard.cn/name: kuboard
  template:
    metadata:
      labels:
        k8s.kuboard.cn/layer: monitor
        k8s.kuboard.cn/name: kuboard
    spec:
      nodeName: your-node-name
      containers:
      - name: kuboard
        image: eipwork/kuboard:latest
        imagePullPolicy: IfNotPresent
      tolerations:
      - key: node-role.kubernetes.io/master
        effect: NoSchedule

---
apiVersion: v1
kind: Service
metadata:
  name: kuboard
  namespace: kube-system
spec:
  type: NodePort
  ports:
  - name: http
    port: 80
    targetPort: 80
    nodePort: 32567
  selector:
    k8s.kuboard.cn/layer: monitor
    k8s.kuboard.cn/name: kuboard

---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: kuboard-user
  namespace: kube-system

---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: kuboard-user
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: cluster-admin
subjects:
- kind: ServiceAccount
  name: kuboard-user
  namespace: kube-system

---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: kuboard-viewer
  namespace: kube-system

---
apiVersion: rbac.authorization.k8s.io/v1
kind: ClusterRoleBinding
metadata:
  name: kuboard-viewer
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: view
subjects:
- kind: ServiceAccount
  name: kuboard-viewer
  namespace: kube-system

# ---
# apiVersion: extensions/v1beta1
# kind: Ingress
# metadata:
#   name: kuboard
#   namespace: kube-system
#   annotations:
#     k8s.kuboard.cn/displayName: kuboard
#     k8s.kuboard.cn/workload: kuboard
#     nginx.org/websocket-services: "kuboard"
#     nginx.com/sticky-cookie-services: "serviceName=kuboard srv_id expires=1h path=/"
# spec:
#   rules:
#   - host: kuboard.yourdomain.com
#     http:
#       paths:
#       - path: /
#         backend:
#           serviceName: kuboard
#           servicePort: http

已复制到剪贴板！

• 执行命令

  kubectl apply -f kuboard-offline.yaml
  

  已复制到剪贴板！

#登录Kuboard

登录 Kuboard 的方式同 安装Kuboard