用官方的部署方法,在 1.24.2上有問題
所以可以將 kuboard 獨立部署
編寫yaml文件
以下配置中請根據實際情況修改
namespace, hostPath, affinity, env, ingress 等這些配置請根據自身環境情況修改,不能完全照抄
#cat kuboard-v3.yaml
---
apiVersion: v1
kind: Service
metadata:
name: kuboard-v3
namespace: yunwei
spec:
# type: NodePort
selector:
app: kuboard-v3
ports:
- name: http
port: 80
targetPort: 80
# nodePort: 31888
---
apiVersion: v1
kind: ReplicationController
metadata:
name: kuboard-v3
namespace: yunwei
spec:
replicas: 1
selector:
app: kuboard-v3
template:
metadata:
labels:
app: kuboard-v3
spec:
affinity:
nodeAffinity:
requiredDuringSchedulingIgnoredDuringExecution:
nodeSelectorTerms:
- matchExpressions:
- key: kubernetes.io/hostname
operator: In
values:
- ctm-k8s-node-86
containers:
- name: kuboard-v3
image: eipwork/kuboard:v3
env:
- name: KUBOARD_ENDPOINT
value: "http://kuboard.ers.tech"
- name: KUBOARD_AGENT_SERVER_UDP_PORT
value: "10081"
- name: KUBOARD_AGENT_SERVER_TCP_PORT
value: "10081"
ports:
- name: httpd
containerPort: 80
- name: udp
containerPort: 10081
- name: tcp
containerPort: 10081
volumeMounts:
- name: kuboard-data
mountPath: /data
volumes:
- name: kuboard-data
hostPath:
path: /data/kuboard-data
---
apiVersion: networking.k8s.io/v1
kind: Ingress
metadata:
name: kuboard-v3
namespace: yunwei
# annotations:
# nginx.ingress.kubernetes.io/secure-backends: "true"
# nginx.ingress.kubernetes.io/ssl-passthrough: "true"
# kubernetes.io/tls-acme: "true"
# cert-manager.io/cluster-issuer: "letsencrypt-prod"
spec:
# tls:
# - hosts:
# - newk8s.ers.com
# secretName: newk8s-ers-tls
ingressClassName: nginx
rules:
- host: kuboard.ers.tech
http:
paths:
- path: /
pathType: Prefix
backend:
service:
name: kuboard-v3
port:
number: 80
運行:
kubectl apply -f kuboard-v3.yaml
等pod運行正常後,即可用瀏覽器打開: http://kuboar.ers.tech 登錄
默認賬號密碼:admin/Kuboard123