【云原生 | Kubernetes 系列】1个POD2个container实现Wordpress K8s部署
2024-05-14 01:09:31
1. Wordpress架构
2. 构建wordpress镜像
2.1 构建nginx-base-wordpress镜像
Dockerfile
FROM harbor.intra.com/baseimages/centos-base:7.9.2009 RUN yum install -y vim wget tree lrzsz gcc gcc-c++ automake pcre pcre-devel zlib zlib-devel openssl openssl-devel iproute net-tools iotop
ADD nginx-1.20.2.tar.gz /usr/local/src/
RUN cd /usr/local/src/nginx-1.20.2 && ./configure --prefix=/apps/nginx && make && make install && ln -sv /apps/nginx/sbin/nginx /usr/sbin/nginx &&rm -rf /usr/local/src/nginx-1.20.2.tar.gz
构建脚本
#!/bin/bash
docker build -t harbor.magedu.net/pub-images/nginx-base-wordpress:v1.20.2 .
sleep 1
docker push harbor.magedu.net/pub-images/nginx-base-wordpress:v1.20.2
构建镜像
root@k8s-master-01:/opt/k8s-data/dockerfile/web/pub-images/nginx-base-wordpress# ./build-command.sh
Successfully built 16a6c56d9d90
Successfully tagged harbor.intra.com/pub-images/nginx-base-wordpress:v1.20.2
The push refers to repository [harbor.intra.com/pub-images/nginx-base-wordpress]
ea1d4eb0d9b4: Pushed
51ea35718443: Pushed
63db03ab1289: Pushed
6f2f514dbcfd: Mounted from wework/redis
42a5df432d46: Mounted from wework/redis
7a6c7dc8d8df: Mounted from wework/redis
c91e83206e44: Mounted from wework/redis
bf0b39b2f6ed: Mounted from wework/redis
174f56854903: Mounted from pub-images/tomcat-base
v1.20.2: digest: sha256:532aa3075b2b32ef89a6ff08b97461df194bd7f38b6a4fc15ac6597b0a75bf14 size: 22112.2 构建nginx-wordpress镜像
Dockerfile
FROM harbor.intra.com/pub-images/nginx-base-wordpress:v1.20.2 ADD nginx.conf /apps/nginx/conf/nginx.conf
ADD run_nginx.sh /apps/nginx/sbin/run_nginx.sh
RUN mkdir -pv /home/nginx/wordpress
RUN useradd nginx -s /sbin/nologin && chown nginx.nginx /home/nginx/wordpress/ -R
EXPOSE 80 443CMD ["/apps/nginx/sbin/run_nginx.sh"]
构建脚本
#!/bin/bash
TAG=$1
docker build -t harbor.intra.com/wework/wordpress-nginx:${TAG} .
echo "镜像制作完成，即将上传至Harbor服务器"
sleep 1
docker push harbor.intra.com/wework/wordpress-nginx:${TAG}
echo "镜像上传完成"
开始构建
root@k8s-master-01:/opt/k8s-data/dockerfile/web/wework/wordpress/nginx# ./build-command.sh v1
Successfully built 8f8cabcb7218
Successfully tagged harbor.intra.com/wework/wordpress-nginx:v1
镜像制作完成，即将上传至Harbor服务器
The push refers to repository [harbor.intra.com/wework/wordpress-nginx]
a10c50297f6e: Pushed
51ae82bfb957: Pushed
c95b7ca8b743: Pushed
dc2fe2b3eba0: Pushed
ea1d4eb0d9b4: Mounted from pub-images/nginx-base-wordpress
51ea35718443: Mounted from pub-images/nginx-base-wordpress
63db03ab1289: Mounted from pub-images/nginx-base-wordpress
6f2f514dbcfd: Mounted from wework/redis
42a5df432d46: Mounted from wework/redis
7a6c7dc8d8df: Mounted from wework/redis
c91e83206e44: Mounted from wework/redis
bf0b39b2f6ed: Mounted from wework/redis
174f56854903: Mounted from wework/jenkins
v1: digest: sha256:1bc3598a70eecf4919a5cf0c952893dafcaf8a9b4740a44fc456e7b520f6eb82 size: 3041
镜像上传完成
root@k8s-master-01:/opt/k8s-data/dockerfile/web/wework/wordpress/nginx# docker images
REPOSITORY TAG IMAGE ID CREATED SIZE
harbor.intra.com/wework/wordpress-nginx v1 8f8cabcb7218 About a minute ago 3.43GB
2.3 构建php镜像
Dockerfile
#PHP Base Image
FROM harbor.intra.com/baseimages/centos-base:7.9.2009 RUN yum install -y https://mirrors.tuna.tsinghua.edu.cn/remi/enterprise/remi-release-7.rpm && yum install php56-php-fpm php56-php-mysql -y
ADD www.conf /opt/remi/php56/root/etc/php-fpm.d/www.conf
ADD run_php.sh /usr/local/bin/run_php.sh
RUN useradd nginx -s /sbin/nologin
EXPOSE 9000CMD ["/usr/local/bin/run_php.sh"]
构建脚本
#!/bin/bash
TAG=$1
docker build -t harbor.intra.com/wework/wordpress-php-5.6:${TAG} .
echo "镜像制作完成，即将上传至Harbor服务器"
sleep 1
docker push harbor.intra.com/wework/wordpress-php-5.6:${TAG}
echo "镜像上传完成"
开始构建镜像
root@k8s-master-01:/opt/k8s-data/dockerfile/web/wework/wordpress/php# ./build-command.sh v1
Successfully built cfbc7d3b9067
Successfully tagged harbor.intra.com/wework/wordpress-php-5.6:v1
镜像制作完成，即将上传至Harbor服务器
The push refers to repository [harbor.intra.com/wework/wordpress-php-5.6]
084c74cb43b5: Pushed
4d89d343ef6a: Pushed
8918bab5ac51: Pushed
6f2f514dbcfd: Mounted from wework/wordpress-nginx
42a5df432d46: Mounted from wework/wordpress-nginx
7a6c7dc8d8df: Mounted from wework/wordpress-nginx
c91e83206e44: Mounted from wework/wordpress-nginx
bf0b39b2f6ed: Mounted from wework/wordpress-nginx
174f56854903: Mounted from wework/wordpress-nginx
v1: digest: sha256:896ffbfc73fe9aa972f6d0aed307fdbd690b75a5172c0139d1c6bb2a844562e1 size: 2413
镜像上传完成
3. Wordpress k8s部署
3.1 pv和pvc
PV配置文件wordpress-persistentvolume.yaml
---
apiVersion: v1
kind: PersistentVolume
metadata:name: wordpress-pvnamespace: wework
spec:capacity:storage: 30GiaccessModes:- ReadWriteOncenfs:server: 192.168.31.109path: /data/k8s/wework/wordpress
PVC配置文件wordpress-persistentvolumeclaim.yaml
---
apiVersion: v1
kind: PersistentVolumeClaim
metadata:name: wordpress-pvcnamespace: wework
spec:volumeName: wordpress-pvaccessModes:- ReadWriteOnceresources:requests:storage: 10Gi
生成pv和pvc
root@k8s-master-01:/opt/k8s-data/yaml/web/wework/wordpress/pv# kubectl apply -f wordpress-persistentvolume.yaml
persistentvolume/wordpress-pv created
root@k8s-master-01:/opt/k8s-data/yaml/web/wework/wordpress/pv# kubectl get pv
NAME CAPACITY ACCESS MODES RECLAIM POLICY STATUS CLAIM STORAGECLASS REASON AGE
jenkins-datadir-pv 100Gi RWO Retain Bound wework/jenkins-datadir-pvc 146m
jenkins-root-datadir-pv 100Gi RWO Retain Bound wework/jenkins-root-data-pvc 146m
mysql-datadir-1 50Gi RWO Retain Bound wework/data-mysql-0 20h
mysql-datadir-2 50Gi RWO Retain Bound wework/data-mysql-3 20h
mysql-datadir-3 50Gi RWO Retain Available 20h
mysql-datadir-4 50Gi RWO Retain Bound wework/data-mysql-1 20h
mysql-datadir-5 50Gi RWO Retain Available 20h
mysql-datadir-6 50Gi RWO Retain Bound wework/data-mysql-2 20h
wordpress-pv 30Gi RWO Retain Available 3s
zookeeper-datadir-pv-1 20Gi RWO Retain Bound wework/zookeeper-datadir-pvc-1 2d13h
zookeeper-datadir-pv-2 20Gi RWO Retain Bound wework/zookeeper-datadir-pvc-2 2d13h
zookeeper-datadir-pv-3 20Gi RWO Retain Bound wework/zookeeper-datadir-pvc-3 2d13h
root@k8s-master-01:/opt/k8s-data/yaml/web/wework/wordpress/pv# kubectl apply -f wordpress-persistentvolumeclaim.yaml
persistentvolumeclaim/wordpress-pvc created
root@k8s-master-01:/opt/k8s-data/yaml/web/wework/wordpress/pv# kubectl get pvc -n wework
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
data-mysql-0 Bound mysql-datadir-1 50Gi RWO 19h
data-mysql-1 Bound mysql-datadir-4 50Gi RWO 19h
data-mysql-2 Bound mysql-datadir-6 50Gi RWO 19h
data-mysql-3 Bound mysql-datadir-2 50Gi RWO 18h
jenkins-datadir-pvc Bound jenkins-datadir-pv 100Gi RWO 144m
jenkins-root-data-pvc Bound jenkins-root-datadir-pv 100Gi RWO 144m
wordpress-pvc Pending wordpress-pv 0 8s
zookeeper-datadir-pvc-1 Bound zookeeper-datadir-pv-1 20Gi RWO 2d13h
zookeeper-datadir-pvc-2 Bound zookeeper-datadir-pv-2 20Gi RWO 2d13h
zookeeper-datadir-pvc-3 Bound zookeeper-datadir-pv-3 20Gi RWO 2d13h
root@k8s-master-01:/opt/k8s-data/yaml/web/wework/wordpress/pv# kubectl get pvc -n wework
NAME STATUS VOLUME CAPACITY ACCESS MODES STORAGECLASS AGE
data-mysql-0 Bound mysql-datadir-1 50Gi RWO 19h
data-mysql-1 Bound mysql-datadir-4 50Gi RWO 19h
data-mysql-2 Bound mysql-datadir-6 50Gi RWO 19h
data-mysql-3 Bound mysql-datadir-2 50Gi RWO 18h
jenkins-datadir-pvc Bound jenkins-datadir-pv 100Gi RWO 144m
jenkins-root-data-pvc Bound jenkins-root-datadir-pv 100Gi RWO 144m
wordpress-pvc Bound wordpress-pv 30Gi RWO 15s
zookeeper-datadir-pvc-1 Bound zookeeper-datadir-pv-1 20Gi RWO 2d13h
zookeeper-datadir-pvc-2 Bound zookeeper-datadir-pv-2 20Gi RWO 2d13h
zookeeper-datadir-pvc-3 Bound zookeeper-datadir-pv-3 20Gi RWO 2d13h
3.2 wordpress应用部署
yaml
kind: Deployment
apiVersion: apps/v1
metadata:labels:app: wordpress-appname: wordpress-app-deploymentnamespace: wework
spec:replicas: 1selector:matchLabels:app: wordpress-apptemplate:metadata:labels:app: wordpress-appspec:containers:- name: wordpress-app-nginximage: harbor.intra.com/wework/wordpress-nginx:v1 imagePullPolicy: Alwaysports:- containerPort: 80protocol: TCPname: http- containerPort: 443protocol: TCPname: httpsvolumeMounts:- name: wordpressmountPath: /home/nginx/wordpressreadOnly: false- name: wordpress-app-phpimage: harbor.intra.com/wework/wordpress-php-5.6:v1#image: harbor.wework.net/wework/php:5.6.40-fpm #imagePullPolicy: IfNotPresentimagePullPolicy: Alwaysports:- containerPort: 9000protocol: TCPname: httpvolumeMounts:- name: wordpressmountPath: /home/nginx/wordpressreadOnly: falsevolumes:- name: wordpresspersistentVolumeClaim:claimName: wordpress-pvc---
kind: Service
apiVersion: v1
metadata:labels:app: wordpress-appname: wordpress-app-specnamespace: wework
spec:type: NodePortports:- name: httpport: 80protocol: TCPtargetPort: 80nodePort: 30031- name: httpsport: 443protocol: TCPtargetPort: 443nodePort: 30033selector:app: wordpress-app
部署yaml
root@k8s-master-01:/opt/k8s-data/yaml/web/wework/wordpress# kubectl apply -f wordpress.yaml
deployment.apps/wordpress-app-deployment created
service/wordpress-app-spec created
root@k8s-master-01:/opt/k8s-data/yaml/web/wework/wordpress# kubectl get pods -n wework
NAME READY STATUS RESTARTS AGE
mysql-0 2/2 Running 0 167m
mysql-1 2/2 Running 0 167m
mysql-2 2/2 Running 0 167m
mysql-3 2/2 Running 0 167m
wework-jenkins-deployment-5697fd66cf-mw8dl 1/1 Running 0 112m
wordpress-app-deployment-67bc78cf9-cn5cf 2/2 Running 0 23s
zookeeper1-699d46468c-62nfk 1/1 Running 0 15h
zookeeper2-7cc484778-fl594 1/1 Running 0 15h
zookeeper3-cdf484f7c-bb9fr 1/1 Running 0 15h
此时Wordpress的Pod已经生成,且该pod里有2个container
root@k8s-master-01:/opt/k8s-data/yaml/web/wework/wordpress# kubectl describe pods wordpress-app-deployment-67bc78cf9-cn5cf -n wework
Name: wordpress-app-deployment-67bc78cf9-cn5cf
Namespace: wework
Priority: 0
Node: 192.168.31.113/192.168.31.113
Start Time: Fri, 12 Aug 2022 11:32:22 +0800
Labels: app=wordpress-apppod-template-hash=67bc78cf9
Annotations: <none>
Status: Running
IP: 172.100.76.167
IPs:IP: 172.100.76.167
Controlled By: ReplicaSet/wordpress-app-deployment-67bc78cf9
Containers:wordpress-app-nginx:Container ID: docker://019dc0ebfd1b23ca2a404a04b627488238355006083dfb60f988a1844df54047Image: harbor.intra.com/wework/wordpress-nginx:v1Image ID: docker-pullable://harbor.intra.com/wework/wordpress-nginx@sha256:051c8810914678d211e60c438b7bf411564bd4b7103494f9dfd20e568dad444ePorts: 80/TCP, 443/TCPHost Ports: 0/TCP, 0/TCPState: RunningStarted: Fri, 12 Aug 2022 11:32:28 +0800Ready: TrueRestart Count: 0Environment: <none>Mounts:/home/nginx/wordpress from wordpress (rw)/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-xpm76 (ro)wordpress-app-php:Container ID: docker://5cff45e252e5ae4991a721df859a927105b19dd663e4f382dfdfdd0a619f2652Image: harbor.intra.com/wework/wordpress-php-5.6:v1Image ID: docker-pullable://harbor.intra.com/wework/wordpress-php-5.6@sha256:896ffbfc73fe9aa972f6d0aed307fdbd690b75a5172c0139d1c6bb2a844562e1Port: 9000/TCPHost Port: 0/TCPState: RunningStarted: Fri, 12 Aug 2022 11:32:34 +0800Ready: TrueRestart Count: 0Environment: <none>Mounts:/home/nginx/wordpress from wordpress (rw)/var/run/secrets/kubernetes.io/serviceaccount from kube-api-access-xpm76 (ro)
Conditions:Type StatusInitialized True Ready True ContainersReady True PodScheduled True
Volumes:wordpress:Type: PersistentVolumeClaim (a reference to a PersistentVolumeClaim in the same namespace)ClaimName: wordpress-pvcReadOnly: falsekube-api-access-xpm76:Type: Projected (a volume that contains injected data from multiple sources)TokenExpirationSeconds: 3607ConfigMapName: kube-root-ca.crtConfigMapOptional: <nil>DownwardAPI: true
QoS Class: BestEffort
Node-Selectors: <none>
Tolerations: node.kubernetes.io/not-ready:NoExecute op=Exists for 300snode.kubernetes.io/unreachable:NoExecute op=Exists for 300s
Events:Type Reason Age From Message---- ------ ---- ---- -------Normal Scheduled 9m53s default-scheduler Successfully assigned wework/wordpress-app-deployment-67bc78cf9-cn5cf to 192.168.31.113Normal Pulling 9m52s kubelet Pulling image "harbor.intra.com/wework/wordpress-nginx:v1"Normal Pulled 9m48s kubelet Successfully pulled image "harbor.intra.com/wework/wordpress-nginx:v1" in 4.186752109sNormal Created 9m47s kubelet Created container wordpress-app-nginxNormal Started 9m47s kubelet Started container wordpress-app-nginxNormal Pulling 9m47s kubelet Pulling image "harbor.intra.com/wework/wordpress-php-5.6:v1"Normal Pulled 9m42s kubelet Successfully pulled image "harbor.intra.com/wework/wordpress-php-5.6:v1" in 5.530956757sNormal Created 9m41s kubelet Created container wordpress-app-phpNormal Started 9m41s kubelet Started container wordpress-app-php
通过控制台访问
创建了index.html后就能通过service转发nginx访问到页面
创建index.php,通过nginx重定向到php
user nginx nginx;
worker_processes auto;
events {worker_connections 1024;
}
http {include mime.types;default_type application/octet-stream;sendfile on;keepalive_timeout 65;client_max_body_size 10M;client_body_buffer_size 16k;client_body_temp_path /apps/nginx/tmp 1 2 2;gzip on;server {listen 80;server_name blogs.magedu.net;location / {root /home/nginx/wordpress;index index.php index.html index.htm;}location ~ \.php$ {root /home/nginx/wordpress;fastcgi_pass 127.0.0.1:9000;fastcgi_index index.php;fastcgi_param SCRIPT_FILENAME $document_root$fastcgi_script_name;include fastcgi_params;}error_page 500 502 503 504 /50x.html;location = /50x.html {root html;}}
}
4. 部署Wordpress应用
4.1 下载并解压Wordpress
下载Wordpress
root@haproxy-1:~# cd /data/k8s/wework/wordpress
root@haproxy-1:/data/k8s/wework/wordpress# wget https://cn.wordpress.org/latest-zh_CN.tar.gz
root@haproxy-1:/data/k8s/wework/wordpress# tar xf latest-zh_CN.tar.gz
root@haproxy-1:/data/k8s/wework/wordpress# mv wordpress/* ./
root@haproxy-1:/data/k8s/wework/wordpress# rm -rf latest-zh_CN.tar.gz wordpress
4.2 配置负载均衡
修改haproxy
listen wordpress-80bind 192.168.31.188:80mode httpserver 192.168.31.111 192.168.31.111:30031 check inter 2s fall 3 rise 5server 192.168.31.112 192.168.31.112:30031 check inter 2s fall 3 rise 5server 192.168.31.113 192.168.31.113:30031 check inter 2s fall 3 rise 5
重启haproxy
root@haproxy-1:~# systemctl restart haproxy
4.3 wordpress数据库创建
mysql-0上
root@mysql-0:/# mysql
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 8975
Server version: 5.7.36-log MySQL Community Server (GPL)Copyright (c) 2000, 2021, Oracle and/or its affiliates.Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.mysql> create database wordpress;
Query OK, 1 row affected (0.00 sec)mysql> grant all privileges on wordpress.* to "wordpress"@"%" identified by "wordpress";
Query OK, 0 rows affected, 1 warning (0.01 sec)## 退出后再试下
root@mysql-0:/# mysql -uwordpress -pwordpress
mysql: [Warning] Using a password on the command line interface can be insecure.
Welcome to the MySQL monitor. Commands end with ; or \g.
Your MySQL connection id is 9096
Server version: 5.7.36-log MySQL Community Server (GPL)Copyright (c) 2000, 2021, Oracle and/or its affiliates.Oracle is a registered trademark of Oracle Corporation and/or its
affiliates. Other names may be trademarks of their respective
owners.Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.mysql> show databases;
+--------------------+
| Database |
+--------------------+
| information_schema |
| wordpress |
+--------------------+
2 rows in set (0.00 sec
这里的数据库主机就是前几日创建的StatefulSet的mysql.
root@haproxy-1:/data/k8s/wework# chown -R 2023.2023 wordpress
【云原生 | Kubernetes 系列】1个POD2个container实现Wordpress K8s部署相关推荐
- 【云原生 | Kubernetes 系列】---Skywalking部署和监控
[云原生 | Kubernetes 系列]-Skywalking部署和监控 1. 分布式链路追踪概念 在较大的web集群和微服务环境中,客户端的一次请求可能需要经过多个不同的模块,多个不同中间件,多个 ...
- 【云原生Kubernetes系列第五篇】kubeadm v1.20 部署K8S 集群架构（人生这道选择题，总会有遗憾）
系列文章目录 ??即日起,更新云原生相关知识,喜欢的小伙伴可以给我点个三连喔 ??收录至专栏 云原生 ??[云原生Docker系列第一篇]Docker镜像管理 ??[云原生Docker系列第二篇]Do ...
- 【云原生 | Kubernetes 系列】--持续交付和持续部署GITOPS(上)
1. 持续交付和持续部署 Continuous Integration Continuous Delivery Continuous Deployment Plan Code Build Test R ...
- 【云原生 | Kubernetes 系列】----污点与容忍
污点与容忍 污点(taints),用于node节点排斥Pod调度.与亲和效果相反.即taint的node排斥Pod的创建. 容忍(toleration),用于Pod容忍Node节点的污点信息.即nod ...
- 【云原生 | Kubernetes 系列】K8s 实战 管理 Secret 详解
kubectl 管理 Secret 前言 一.使用 kubectl 管理 Secret 1.1.创建 Secret 1.2.验证 Secret 1.3.解码 Secret 1.4.清理 二.使用配置文 ...
- 【云原生 | Kubernetes 系列】K8s 实战 一文学会如何从 PodSecurityPolicy 迁移到内置的 PodSecurity 准入控制器
PodSecurityPolicy 迁移到内置的 PodSecurity 准入控制器 前言 一.Pod 安全性 二.访问权限 三.标准化 PodSecurityPolicy 3.1.去掉纯粹变更性质的 ...
- 【云原生 | Kubernetes 系列】--Gitops持续交付 Tekton Pipeline使用进阶(pvc和Results)
Tekton Pipeline使用进阶 1. 基于Maven项目构建 主要实现source to package的过程 包含2个Task: fetch-from-source和build 使用pvc实 ...
- 【云原生 | Kubernetes 系列】--Gitops持续交付和持续Tekton Triggers
Tekton Triggers Tekton 几个项目 Tekton Pipelines Task Steps:执行具体操作,在容器中执行的命令或脚本 command script TaskRun 运 ...
- 【云原生 | Kubernetes 系列】---CephFS和OSS
1. CephFS ceph fs即ceph filesystem,可以实现文件系统共享功能,客户端通过ceph协议挂载并使用ceph集群作为数据存储服务器. Ceph FS需要运行Meta Data ...
最新文章
- SpringBoot (七) ：SpringBoot 整合dubbo
- 【Android 逆向】Android 逆向通用工具开发 ( PC 端工程分析 | 网络初始化操作 | PC 端工程核心业务逻辑 )
- 数据中心怎么建更科学
- 给php权限,PHP实现权限管理功能的方法
- react提交数据到数据库_React型关系数据库事务
- v-if、v-for、v-model、v-on
- 市监总局对橙心优选等五家社区团购不正当价格行为作出行政处罚
- pthread_mutex_lock的作用
- VHD容量调整的方法（保存原有vhd）
- css的font修改颜色,css的font字体颜色如何设置
- 【新闻发布系统】登录和注销的实现
- 用ODBC方式操作dbf文件
- c++实现右下角弹窗
- Xavier(2):Xavier NX刷机步骤及报错解决
- 全民远程办公的第一天，为什么你的视频会议卡住了？
- 利用无障碍服务自动获取微信号
- gerrit安装配置（http反向代理）
- h3c trunk口改access_H3C交换机端口链路类型Trunk 端口配置指导
- 区块链潮起：行业人才紧缺 欧科云链何以“职”得去？
- Caché程序员必须知道符号与缩写 第二章 ObjectScript中使用的缩写