在k3s中部署OrdinaryRoad（一）

苗锦洲

创建于：2022-04-27 18:41:18

294

手上有两台服务器，想组个集群部署一下 k3s 玩玩，部署 MySQL、Redis 和 Nacos

容器化

Podman k3s

友情提示：此篇文章大约需要阅读 35分20秒

Podman

Podman 添加私有镜像源配置 registries.conf_Kiritow 的博客-CSDN 博客_podman registry

Docker 私有镜像仓库 - 一杯水 M - 博客园 (cnblogs.com)

搭建镜像仓库

Docker 官方的 Docker Registry 是一个基础版本的 Docker 镜像仓库，具备仓库管理的完整功能，但是没有图形化界面。

搭建方式比较简单，命令如下：


podman run -d \
    --restart=always \
    --name registry    \
    -p 5000:5000 \
    -v registry-data:/var/lib/registry \
    registry

命令中挂载了一个数据卷 registry-data 到容器内的/var/lib/registry 目录，这是私有镜像库存放数据的目录。

访问http://YourIp:5000/v2/_catalog 可以查看当前私有镜像服务中包含的镜像


curl http://localhost:5000/v2/_catalog

修改配置

其中 prefix 是 pull 的时候指定的镜像前缀，location 是获取镜像的地址，如果不指定 prefix 则默认和 location 一致。insecure=true 表示允许通过 HTTP 协议来获取镜像，对于私有化部署/内网测试环境下无 https 证书的环境来说很有帮助。


# /etc/containers/registries.conf

[[registry]]
prefix = "10.0.12.13:5000"
location = "10.0.12.13:5000"
insecure = true

修改默认端口范围 30000-32767

编辑 kube-apiserver.yaml 文件


vi /etc/systemd/system/k3s.service

**修改 ExecStart，加上 **--kube-apiserver-arg service-node-port-range=1-65535


ExecStart=/usr/local/bin/k3s server --kube-apiserver-arg service-node-port-range=1-65535

重启 kubelet


systemctl daemon-reload
systemctl restart k3s

创建 Namespace

名字空间 | Kubernetes

控制台创建


apiVersion: v1
kind: Namespace
metadata:
  name: YOUR_NAMESPACE_NAME

查看 namespace


kubectl get namespaces

设置名字空间偏好

你可以永久保存名字空间，以用于对应上下文中所有后续 kubectl 命令。


kubectl config set-context --current --namespace=or-dev
# 验证之
kubectl config view | grep namespace:

创建有状态应用 MySQL

jnC8ZVj!TL%PJe8n

示例：使用 Persistent Volumes 部署 WordPress 和 MySQL | Kubernetes

创建 kustomization.yaml

创建 Secret 生成器

**A **Secret 是存储诸如密码或密钥之类的敏感数据的对象。从 1.14 开始，kubectl 支持使用 kustomization 文件管理 Kubernetes 对象。您可以通过 kustomization.yaml 中的生成器创建一个 Secret。

通过以下命令在 kustomization.yaml 中添加一个 Secret 生成器。您需要用您要使用的密码替换 YOUR_PASSWORD。


# /root/ordinaryroad/or-mysql/kustomization.yaml

cat <<EOF >./kustomization.yaml
secretGenerator:
- name: mysql-pass
  namespace: or-dev
  literals:
  - password=YOUR_PASSWORD
EOF

单实例 MySQL

以下 manifest 文件描述了单实例 MySQL 部署。MySQL 容器将 PersistentVolume 挂载在 /var/lib/mysql。 MYSQL_ROOT_PASSWORD 环境变量设置来自 Secret 的数据库密码。


# /root/ordinaryroad/or-mysql/mysql-deployment.yaml

apiVersion: v1
kind: Service
metadata:
  name: mysql
  namespace: or-dev
spec:
  type: NodePort           # 配置为NodePort，外部可以访问
  ports:
    - port: 3306
      targetPort: 3306     # 容器暴露的端口，与Dockerfile暴露端口保持一致
      nodePort: 3306       # NodePort，外部访问的端口
  selector:
    tier: mysql
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: mysql-pv-claim
  namespace: or-dev
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 20Gi
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: mysql
  namespace: or-dev
spec:
  selector:
    matchLabels:
      tier: mysql
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        tier: mysql
    spec:
      containers:
      - image: mysql/mysql-server:8.0.26
        name: mysql
        env:
        - name: TZ
          value: Asia/Shanghai
        - name: MYSQL_ROOT_PASSWORD
          valueFrom:
            secretKeyRef:
              name: mysql-pass
              key: password
        ports:
        - containerPort: 3306
          name: mysql
        volumeMounts:
        - name: mysql-persistent-storage
          mountPath: /var/lib/mysql
      volumes:
      - name: mysql-persistent-storage
        persistentVolumeClaim:
          claimName: mysql-pv-claim

补充到 `kustomization.yaml` 文件。


# /root/ordinaryroad/or-mysql/kustomization.yaml

cat <<EOF >>./kustomization.yaml
resources:
  - mysql-deployment.yaml
EOF

应用

kustomization.yaml 包含用于部署 WordPress 网站的所有资源以及 MySQL 数据库。您可以通过以下方式应用目录


kubectl apply -k ./


secret/or-mysql-pass-2fg88hk64d created
service/or-mysql created
deployment.apps/or-mysql created
persistentvolumeclaim/or-mysql-pv-claim created

创建有状态应用 Redis

使用 ConfigMap 来配置 Redis | Kubernetes

kustomization.yaml


# /root/ordinaryroad/or-redis/kustomization.yaml
resources:
  - redis-config.yaml
  - redis-deployment.yaml

redis-config.yaml


# /root/ordinaryroad/or-redis/redis-config.yaml

apiVersion: v1
kind: ConfigMap
metadata:
  name: redis-config
  namespace: or-dev
data:
  redis-config: |
    bind '* -::*'

redis-deployment.yaml


# /root/ordinaryroad/or-redis/redis-deployment.yaml

apiVersion: v1
kind: Service
metadata:
  name: redis
  namespace: or-dev
spec:
  type: NodePort           # 配置为NodePort，外部可以访问
  ports:
    - port: 6379
      targetPort: 6379     # 容器暴露的端口，与Dockerfile暴露端口保持一致
      nodePort: 6379       # NodePort，外部访问的端口
  selector:
    tier: redis
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: redis-pv-claim
  namespace: or-dev
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 10Gi
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: redis
  namespace: or-dev
spec:
  selector:
    matchLabels:
      tier: redis
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        tier: redis
    spec:
      containers:
      - image: redis:6.2.6
        name: redis
        ports:
        - containerPort: 6379
          name: redis
        volumeMounts:
        - name: redis-persistent-storage
          mountPath: /data
        - name: redis-config
          mountPath: /usr/local/etc/redis
      volumes:
      - name: redis-persistent-storage
        persistentVolumeClaim:
          claimName: redis-pv-claim
      - name: redis-config
        configMap:
          name: redis-config
          items:
            - key: redis-config
              path: redis.conf

应用


kubectl apply -k ./


configmap/redis-config created
service/redis created
deployment.apps/redis created
persistentvolumeclaim/redis-pv-claim created

创建无状态应用 Nacos

kustomization.yaml


# /root/ordinaryroad/nacos/kustomization.yaml

secretGenerator:
- name: nacos-mysql-pass
  namespace: or-dev
  literals:
  - password=jnC8ZVj!TL%PJe8n
resources:
  - nacos-deployment.yaml

nacos-deployment.yaml


# /root/ordinaryroad/nacos/nacos-deployment.yaml

apiVersion: v1
kind: Service
metadata:
  name: nacos
  namespace: or-dev
spec:
  type: NodePort           # 配置为NodePort，外部可以访问
  ports:
    - port: 8848
      targetPort: 8848     # 容器暴露的端口，与Dockerfile暴露端口保持一致
      nodePort: 8848       # NodePort，外部访问的端口
  selector:
    tier: nacos
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: nacos
  namespace: or-dev
spec:
  selector:
    matchLabels:
      tier: nacos
  replicas: 1
  template:
    metadata:
      labels:
        tier: nacos
    spec:
      containers:
      - name: nacos
        image: nacos/nacos-server:v2.0.4
        env:
        - name: PREFER_HOST_MODE
          value: "hostname"
        - name: MODE
          value: "standalone"
        - name: SPRING_DATASOURCE_PLATFORM
          value: "mysql"
        - name: MYSQL_SERVICE_DB_PARAM
          value: "useUnicode=true&characterEncoding=utf-8&useSSL=false&useLegacyDatetimeCode=false&serverTimezone=GMT%2B8&allowPublicKeyRetrieval=true"
        - name: MYSQL_SERVICE_HOST
          value: "mysql.or-dev"
        - name: MYSQL_SERVICE_DB_NAME
          value: "or_config_pro"
        - name: MYSQL_SERVICE_PORT
          value: "3306"
        - name: MYSQL_SERVICE_USER
          value: "root"
        - name: MYSQL_SERVICE_PASSWORD
          valueFrom:
            secretKeyRef:
              name: nacos-mysql-pass
              key: password
        ports:
        - containerPort: 8848
          name: nacos

使用 Ingress 暴露服务

Ingress | Kubernetes

k8s-(七）暴露服务的三种方式新林。的博客-CSDN 博客k8s 服务暴露

k8s-(八）通过 Ingress-nginx 暴露 service 给外部网络访问新林。的博客-CSDN 博客spanking 外网

步骤一，创建 Ingress 的 YAML 描述文件
首先创建ingress-nginx 的文件目录（后面创建的ingress 相关的文件都在这里面，便于维护）
mkdir ingress-nginx
创建一个名称为 deploy.yaml，内容如下
注：
1.这个 YAML 描述文件有点长，简单描述一下，里面主要创建了一个ingress-nginx 的命名空间，nginx-ingress-controller 的 Deployment 对象以及最后面创建ingress-nginx 的 Service，Service 配置映射的端口
2.我安装的 k8s 版本是 1.18.0


kind: ConfigMap
apiVersion: v1
metadata:
  name: nginx-configuration
  namespace: or-dev
  labels:
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
---
kind: ConfigMap
apiVersion: v1
metadata:
  name: tcp-services
  namespace: or-dev
  labels:
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
---
kind: ConfigMap
apiVersion: v1
metadata:
  name: udp-services
  namespace: or-dev
  labels:
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: default-http-backend
  namespace: or-dev
  labels:
    app: default-http-backend
spec:
  replicas: 1
  selector:
    matchLabels:
      app: default-http-backend
  template:
    metadata:
      labels:
       app: default-http-backend
    spec:
      terminationGracePeriodSeconds: 60
      containers:
      - name: default-http-backend
        image:  registry.cn-qingdao.aliyuncs.com/kubernetes_xingej/defaultbackend-amd64:1.5      #建议提前在node节点下载镜像；
        livenessProbe:
          httpGet:
            path: /healthz
            port: 8080
            scheme: HTTP
          initialDelaySeconds: 30
          timeoutSeconds: 5
        ports:
        - containerPort: 8080
        resources:
         # 这里调整了cpu和memory的大小，可能不同集群限制的最小值不同，看部署失败的原因就清楚
          limits:
            cpu: 100m
            memory: 100Mi
          requests:
            cpu: 100m
            memory: 100Mi
---
apiVersion: v1
kind: Service
metadata:
  name: default-http-backend
  namespace: or-dev
  labels:
    app: default-http-backend
spec:
  ports:
  - port: 80
    targetPort: 8080
  selector:
    app: default-http-backend
---
apiVersion: v1
kind: ServiceAccount
metadata:
  name: nginx-ingress-serviceaccount
  namespace: or-dev
  labels:
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRole
metadata:
  name: nginx-ingress-clusterrole
  labels:
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
rules:
  - apiGroups:
      - ""
    resources:
      - configmaps
      - endpoints
      - nodes
      - pods
      - secrets
    verbs:
      - list
      - watch
  - apiGroups:
      - ""
    resources:
      - nodes
    verbs:
      - get
  - apiGroups:
      - ""
    resources:
      - services
    verbs:
      - get
      - list
      - watch
  - apiGroups:
      - ""
    resources:
      - events
    verbs:
      - create
      - patch
  - apiGroups:
      - "extensions"
      - "networking.k8s.io"
    resources:
      - ingresses
    verbs:
      - get
      - list
      - watch
  - apiGroups:
      - "extensions"
      - "networking.k8s.io"
    resources:
      - ingresses/status
    verbs:
      - update
---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: Role
metadata:
  name: nginx-ingress-role
  namespace: or-dev
  labels:
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
rules:
  - apiGroups:
      - ""
    resources:
      - configmaps
      - pods
      - secrets
      - namespaces
    verbs:
      - get
  - apiGroups:
      - ""
    resources:
      - configmaps
    resourceNames:
      # Defaults to "<election-id>-<ingress-class>"
      # Here: "<ingress-controller-leader>-<nginx>"
      # This has to be adapted if you change either parameter
      # when launching the nginx-ingress-controller.
      - "ingress-controller-leader-nginx"
    verbs:
      - get
      - update
  - apiGroups:
      - ""
    resources:
      - configmaps
    verbs:
      - create
  - apiGroups:
      - ""
    resources:
      - endpoints
    verbs:
      - get
---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: RoleBinding
metadata:
  name: nginx-ingress-role-nisa-binding
  namespace: or-dev
  labels:
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: Role
  name: nginx-ingress-role
subjects:
  - kind: ServiceAccount
    name: nginx-ingress-serviceaccount
    namespace: or-dev
---
apiVersion: rbac.authorization.k8s.io/v1beta1
kind: ClusterRoleBinding
metadata:
  name: nginx-ingress-clusterrole-nisa-binding
  labels:
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
roleRef:
  apiGroup: rbac.authorization.k8s.io
  kind: ClusterRole
  name: nginx-ingress-clusterrole
subjects:
  - kind: ServiceAccount
    name: nginx-ingress-serviceaccount
    namespace: or-dev
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx-ingress-controller
  namespace: or-dev
  labels:
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
spec:
  replicas: 2
  selector:
    matchLabels:
      app.kubernetes.io/name: ingress-nginx
      app.kubernetes.io/part-of: ingress-nginx
  template:
    metadata:
      labels:
        app.kubernetes.io/name: ingress-nginx
        app.kubernetes.io/part-of: ingress-nginx
      annotations:
        prometheus.io/port: "10254"
        prometheus.io/scrape: "true"
    spec:
      # wait up to five minutes for the drain of connections
      terminationGracePeriodSeconds: 300
      serviceAccountName: nginx-ingress-serviceaccount
      nodeSelector:
        kubernetes.io/os: linux
      containers:
        - name: nginx-ingress-controller
          image: suisrc/ingress-nginx:0.30.0   #建议提前在node节点下载镜像；
          args:
            - /nginx-ingress-controller
            - --default-backend-service=$(POD_NAMESPACE)/default-http-backend
            - --configmap=$(POD_NAMESPACE)/nginx-configuration
            - --tcp-services-configmap=$(POD_NAMESPACE)/tcp-services
            - --udp-services-configmap=$(POD_NAMESPACE)/udp-services
            - --publish-service=$(POD_NAMESPACE)/ingress-nginx
            - --annotations-prefix=nginx.ingress.kubernetes.io
          securityContext:
            allowPrivilegeEscalation: true
            capabilities:
              drop:
                - ALL
              add:
                - NET_BIND_SERVICE
            # www-data -> 101
            runAsUser: 101
          env:
            - name: POD_NAME
              valueFrom:
                fieldRef:
                  fieldPath: metadata.name
            - name: POD_NAMESPACE
              valueFrom:
                fieldRef:
                  fieldPath: metadata.namespace
          ports:
            - name: http
              containerPort: 80
              protocol: TCP
            - name: https
              containerPort: 443
              protocol: TCP
          livenessProbe:
            failureThreshold: 3
            httpGet:
              path: /healthz
              port: 10254
              scheme: HTTP
            initialDelaySeconds: 10
            periodSeconds: 10
            successThreshold: 1
            timeoutSeconds: 10
          readinessProbe:
            failureThreshold: 3
            httpGet:
              path: /healthz
              port: 10254
              scheme: HTTP
            periodSeconds: 10
            successThreshold: 1
            timeoutSeconds: 10
          lifecycle:
            preStop:
              exec:
                command:
                  - /wait-shutdown
---
apiVersion: v1
kind: LimitRange
metadata:
  name: ingress-nginx
  namespace: or-dev
  labels:
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
spec:
  limits:
  - min:
      memory: 90Mi
      cpu: 100m
    type: Container
---
apiVersion: v1
kind: Service
metadata:
  name: ingress-nginx
  namespace: or-dev
  labels:
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx
spec:
  type: NodePort
  ports:
    - name: http
      port: 80
      targetPort: 80
      protocol: TCP
      # HTTP
      nodePort: 80
    - name: https
      port: 443
      targetPort: 443
      protocol: TCP
     # HTTPS
      nodePort: 443
  selector:
    app.kubernetes.io/name: ingress-nginx
    app.kubernetes.io/part-of: ingress-nginx

本文作者：苗锦洲

本文链接：https://blog.ordinaryroad.tech/1/article/75

Podman入门

可以滚动的View设置padding和scrollbar需要注意

Podman

搭建镜像仓库

修改配置

修改默认端口范围 30000-32767

创建 Namespace

查看 namespace

设置名字空间偏好

创建有状态应用 MySQL

创建 kustomization.yaml

创建 Secret 生成器

单实例 MySQL

补充到 kustomization.yaml 文件。

应用

创建有状态应用 Redis

kustomization.yaml

redis-config.yaml

redis-deployment.yaml

应用

创建无状态应用 Nacos

kustomization.yaml

nacos-deployment.yaml

使用 Ingress 暴露服务

补充到 `kustomization.yaml` 文件。