Solo 可以部署在 K8S 上面么？

高射炮打蚊子吗，k8s 觉得很屈才 😄

可以 编写两个 yaml 文件

apiVersion: apps/v1
kind: StatefulSet
metadata:
  name: solo
  namespace: b3log
spec:
  replicas: 1
  selector:
    matchLabels:
      app: solo
  serviceName: solo
  template:
    metadata:
      name: solo
      labels:
        app: solo
    spec:
      tolerations:
      - key: "node.kubernetes.io/unreachable"
        operator: "Exists"
        effect: "NoExecute"
        tolerationSeconds: 60
      - key: "node.kubernetes.io/not-ready"
        operator: "Exists"
        effect: "NoExecute"
        tolerationSeconds: 60
      affinity:                                       # 亲和性
        nodeAffinity:                              # Pod亲和性
          requiredDuringSchedulingIgnoredDuringExecution:   # 硬要求
            nodeSelectorTerms:
            - matchExpressions:
              - key: node                             # 根据label是node的键来配对
                operator: In                          # 适用表达式
                values:                               # 值如下
                - master                              # 调度到有master标签的节点
        podAntiAffinity:                              # 如果检测到节点有{app:postgres}则不部署，避免postgres在同一节点重复部署
          requiredDuringSchedulingIgnoredDuringExecution:
          - labelSelector:
              matchExpressions:
              - key: app
                operator: In
                values:
                - solo
            topologyKey: "kubernetes.io/hostname"
      terminationGracePeriodSeconds: 0                # 异常立即删除
      containers:
      - name: solo
        securityContext:
          privileged: true
        image: b3log/solo:latest
        imagePullPolicy: IfNotPresent
        ports:
        - name: solo
          containerPort: 8080
        env:
        - name: TZ
          value: Asia/Shanghai
        - name: RUNTIME_DB
          value: "MYSQL"
        - name: JDBC_USERNAME
          value: "root"
        - name: JDBC_PASSWORD
          value: "root"
        - name: JDBC_DRIVER
          value: "com.mysql.cj.jdbc.Driver"
        - name: JDBC_URL
          value: "jdbc:mysql://192.168.1.222:3306/solo?useUnicode=yes&characterEncoding=UTF-8&useSSL=false&serverTimezone=UTC&allowPublicKeyRetrieval=true"
      volumes:
      - name: tz
        hostPath:
          path: /etc/localtime

apiVersion: v1
kind: Service
metadata:
  name: solo
  namespace: b3log
  labels:
    app: solo
spec:
  ports:
  - port: 8080
    targetPort: 8080
    name: solo
  clusterIP: None
  selector:
    app: solo
---
apiVersion: v1
kind: Service
metadata:
  name: solo-service
  namespace: b3log
  labels:
    app: solo
spec:
  externalIPs:               # 暴露Service到外部IP
  - 192.168.1.228               # IP
  selector:
    app: solo
  ports:
    - protocol: TCP
      port: 8080
      targetPort: 8080
      name: solo

1. pull solo 最新镜像
2. 8080 网络端口在公网上是否通，排除防火墙影响
3. 检查 docker solo 启动参数 listen_port 和 server_port，这两个端口含义不一样，具体请参考文档
4. 数据库端口不要暴露在公网上
5. 使用 NGINX 反代

主要是 solo 没必要部署在 k8s 上吧