Create PHP message board system with kubernetes

This article will demonstrate the use of kubernetes The system is based on kubeguide Related image files are created based on php and Redis Message board system of , Because the system resources are limited ,kubernetes colony only one master Nodes and slave node .

Docker Local warehouse and kubernetes colony Please check the configuration https://www.linuxidc.com/Linux/2018-03/151136.htm.

One 、 Introduction to the environment Operating system version ：CentOS linux 7.2 64bit Master node ：192.168.115.5/24 vm1 Slave node 1：192.168.115.6/24 vm2

The access flow chart is as follows ：

Two 、 Download relevant image files online , And incorporated into the local warehouse for unified management

# docker pull kubeguide/redis-master # docker pull kubeguide/guestbook-php-frontend # docker pull kubeguide/guestbook-redis-slave # docker tag kubeguide/redis-master registry.fjhb.cn/redis-master # docker tag kubeguide/guestbook-php-frontend registry.fjhb.cn/guestbook-php-frontend # docker tag kubeguide/guestbook-redis-slave registry.fjhb.cn/guestbook-redis-slave # docker push registry.fjhb.cn/redis-master # docker push registry.fjhb.cn/guestbook-php-frontend # docker push registry.fjhb.cn/guestbook-redis-slave # curl -u yang:123 -XGET https://registry.fjhb.cn/v2/_catalog # docker images |grep fjhb

3、 ... and 、 Configuration file preparation 1、 establish redis-master rc and service The configuration file

# cat redis-master-controller.yaml apiVersion: v1 kind: ReplicationController metadata:   name: redis-master spec:   replicas: 1   selector:     name: redis-master   template:     metadata:       name: redis-master       labels:         name: redis-master     spec:       containers:       - name: redis-master         image: registry.fjhb.cn/redis-master         ports:         - containerPort: 6379# cat redis-master-service.yaml apiVersion: v1 kind: Service metadata:   name: redis-master   labels:     name: redis-master spec:   ports:   - port: 6379     targetPort: 6379   selector: name: redis-master

2、 establish redis-slave Of rc and service The configuration file

# cat redis-slave-controller.yaml apiVersion: v1 kind: ReplicationController metadata:   name: redis-slave spec:   replicas: 2   selector:     name: redis-slave   template:     metadata:       name: redis-slave       labels:         name: redis-slave     spec:       containers:       - name: redis-slave         image: registry.fjhb.cn/guestbook-redis-slave         env:         - name: GET_HOSTS_FROM           value: env         ports:         - containerPort: 6379# cat redis-slave-service.yaml apiVersion: v1 kind: Service metadata:   name: redis-slave   labels:     name: redis-slave spec:   ports:   - port: 6379   selector: name: redis-slave

3、 establish frontend Of rc and service The configuration file

# cat frontend-controller.yaml apiVersion: v1 kind: ReplicationController metadata:   name: frontend   labels:     name: frontend spec:   replicas: 3   selector:     name: frontend   template:     metadata:       labels:         name: frontend     spec:       containers:       - name: frontend         image: registry.fjhb.cn/guestbook-php-frontend         env:         - name: GET_HOSTS_FROM           value: env         ports:         - containerPort: 80# cat frontend-service.yaml apiVersion: v1 kind: Service metadata:   name: frontend   labels:     name: frontend spec:   type: NodePort   ports:   - port: 80     nodePort: 30001   selector: name: frontend

Four 、 stay master Create... On node rc and sevices

# kubectl create -f redis-master-controller.yaml # kubectl create -f redis-slave-controller.yaml # kubectl create -f frontend-controller.yaml # kubectl create -f redis-master-service.yaml # kubectl create -f redis-slave-service.yaml # kubectl create -f frontend-service.yaml # kubectl get rc # kubectl get svc # kubectl get pod

# kubectl describe pod redis-slave-gsk1p

could not be built pod The main reason is that the image cannot be pulled from the local warehouse , Even if the image already exists locally , Also report this error . because kubernetes Of imagePullPolicy The default value of the image policy is Always

From our local warehouse nginx Configured with basic verification , Therefore, the error is reported as follows Error syncing pod, skipping: failed to "StartContainer" for "redis-slave" with ErrImagePull: "unauthorized: authentication required" close nginx basic After certification , Try again , Sure enough, there is no problem .

stay Kubernetes Use private warehouses in and support basic The final solution of authentication is to configure kubernetes Of serviceaccount, The detailed configuration will be introduced in subsequent articles .

6、 ... and 、 test 1、 see redis master Node redis colony Information

# kubectl exec redis-master-9993n redis-cli info |grep -A 5 "Replication" # kubectl exec redis-slave-gnq41 redis-cli info |grep -A 5 "Replication" # kubectl exec redis-slave-nvscp redis-cli info |grep -A 5 "Replication"

2、web test

adopt firebug The plug-in can be seen as php+apache In providing web service

7、 ... and 、 rc and service The deletion of

# kubectl delete -f frontend-controller.yaml # kubectl delete -f redis-master-controller.yaml # kubectl delete -f redis-slave-controller.yaml # kubectl delete -f redis-slave-service.yaml # kubectl delete -f redis-master-service.yaml # kubectl delete -f frontend-service.yaml