在k8s中以deployment方式部署minio

minio官网给的demo是通过pod方式部署的，我碰到了好几次因为k8s集群断电重启后，以单pod方式部署部署的minio消失。因此这里改用deplyment的方式部署minio。

以下是完整的minio部署清单

---
# Deploys a new MinIO Pod into the metadata.namespace Kubernetes namespace
#
# The `spec.containers[0].args` contains the command run on the pod
# The `/data` directory corresponds to the `spec.containers[0].volumeMounts[0].mountPath`
# That mount path corresponds to a Kubernetes HostPath which binds `/data` to a local drive or volume on the worker node where the pod runs
#
apiVersion: apps/v1
kind: Deployment
metadata:
  name: minio
  namespace: devops
spec:
  replicas: 1
  selector:
    matchLabels:
      app: minio
  template:
    metadata:
      labels:
        app: minio
    spec:
      containers:
      - name: minio
        image: 192.168.10.30:9000/minio:latest
        command:
        - /bin/bash
        - -c
        args:
        - minio server /data --console-address :9001
        env:
          - name: MINIO_SERVER_URL
            value: 'http://minio.rockstics.com'
          - name: MINIO_BROWSER_REDIRECT_URL
            value: 'http://minio.rockstics.com/minio/ui'
        volumeMounts:
        - mountPath: /data
          name: localvolume # Corresponds to the `spec.volumes` Persistent Volume
      hostAliases:
        - ip: "192.168.10.188"
          hostnames:
          - "minio.rockstics.com"
      volumes:
      - name: localvolume
        hostPath: # MinIO generally recommends using locally-attached volumes
          path: /data/minio # Specify a path to a local drive or volume on the Kubernetes worker node
          type: DirectoryOrCreate # The path to the last directory must exist
      nodeSelector:
        kubernetes.io/hostname: kubernetesw02

---
kind: Service
apiVersion: v1
metadata:
  name: minio-server
  namespace: devops
  labels:
    app: minio-server
spec:
  ports:
    - name: http-console
      protocol: TCP
      port: 9001
      targetPort: 9001
    - name: http-api
      protocol: TCP
      port: 9000
      targetPort: 9000
  selector:
    app: minio
---
apiVersion: traefik.containo.us/v1alpha1
kind: IngressRoute
metadata:
  annotations:
  labels:
    app: minio
  name: minio
  namespace: devops
spec:
  routes:
    - kind: Rule
      match: Host(`minio.isiact.com`)
      services:
        - kind: Service
          name: minio-server
          namespace: devops
          port: http-api
    - kind: Rule
      match: Host(`minio.isiact.com`) && PathPrefix(`/minio/ui`)
      middlewares:
        - name: minio-console
      services:
        - kind: Service
          name: minio-server
          namespace: devops
          port: http-console
---
apiVersion: traefik.containo.us/v1alpha1
kind: Middleware
metadata:
  annotations:
  name: minio-console
  namespace: devops
spec:
  stripPrefix:
    prefixes:
      - /minio/ui

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109

题外话：由于我通过MINIO_SERVER_URL指定了minio的内网访问域名，导致登录minio报"invalid login"的问题，刚开始以为是挂载的数据路径中有.minio.sys 相关信息（包括minio配置信息包括用户密码，assce_key等信息）被其他容器挂载无效，实践证明不是这样的，后来才发现是因为容易内无法解析我的内网域名导致的，解决方案就是直接进行host绑定。