linux怎么查看本机内存大小
282
2022-10-30
Deployment
Deployment
Deployment:kind: DeploymentapiVersion: extensions/v1beta1metadata:name: skxspec:replicas: 3template:metadata:labels:app: skx_serverspec:containers:
name: 192.168.1.10:5000/httpd:v1ports: containerPort: 80
PS：注意，在Deployment资源对象中，可以添加Port字段，但此字段仅供用户查看，并不实际生效。如下：ports:
containerPort: 80
SERVICE
kind: ServiceapiVersion: v1metadata:name: skx-svcspec:selector:app: skx_serverports:
protocol: TCPport: 80targetPort: 80
关联主机：kind: ServiceapiVersion: v1metadata:name: skx-svcspec:type: NodePortselector:app: skx_serverports:
protocol: TCPport: 80targetPort: 80nodePort: 30123更改pod访问界面：[root@master ~]# kubectl exec -it skx-694cc5db89-45nvk /bin/bashroot@skx-694cc5db89-45nvk:/usr/local/apache2# echo no.1 > htdocs/index.htmlroot@skx-694cc5db89-45nvk:/usr/local/apache2# exit查看规则：[root@master ~]# iptables-save SNAT：Source NAT(源地址转换) DNAT：Destnation(目标地址转换) MASQ：动态的源地址转换Service实现的负载均衡使用的时iptables规则。IPVS10.107.64.232KUBE-SVC-QDLMDMK46RWAY7QJ
与[root@master ~]# kubectl get pod -o wide
回滚到指定版本：删除之前创建的资源：[root@master ~]# kubectl delete -f skx-svc.yaml service "skx-svc" deleted[root@master ~]# kubectl delete -f skx.yaml deployment.extensions "skx" deleted
[root@master ~]# kubectl get deployments.No resources found.[root@master ~]# vim skx.yaml kind: DeploymentapiVersion: extensions/v1beta1metadata:name: skxspec:revisionHistoryLimit: 10 //添加replicas: 3template:metadata:labels:app: skx_serverspec:containers:
name: 192.168.1.10:5000/httpd:v1ports: containerPort: 80准备三个版本所使用的私有镜像，来模拟每次升级不同的镜像。[root@master ~]# mv skx.yaml skx1.yaml[root@master ~]# cp skx1.yaml skx2.yaml[root@master ~]# cp skx1.yaml skx3.yaml
[root@master ~]# vim skx1.yaml
15行：
image: 192.168.1.10:5000/~]# vim skx2.yaml
15行：
image: 192.168.1.10:5000/~]# vim skx3.yaml
15行：
image: 192.168.1.10:5000/~]# kubectl apply -f skx1.yaml --record deployment.extensions/skx created[root@master ~]# kubectl apply -f skx2.yaml --record deployment.extensions/skx configured[root@master ~]# kubectl apply -f skx3.yaml --record deployment.extensions/skx configured查看有哪些版本信息[root@master ~]# kubectl rollout history deployment skx deployment.extensions/skx REVISION CHANGE-CAUSE1 kubectl apply --filename=skx1.yaml --record=true2 kubectl apply --filename=skx2.yaml --record=true3 kubectl apply --filename=skx3.yaml --record=true
运行并升级Deployment资源，并记录版本信息。[root@master ~]# kubectl apply -f skx2.yaml --record deployment.extensions/skx configured此时可以运行一个关联的Service自愿去验证，升级是否成功[root@master ~]# kubectl apply -f skx-svc.yaml service/skx-svc created
[root@master ~]# kubectl get svcNAME TYPE CLUSTER-IP EXTERNAL-IP PORT(S) AGE NodePort 10.97.81.154
[root@master ~]# curl 10.96.174.199
songkaixiong | test-web | | v3
回滚到指定版本。[root@master ~]# kubectl rollout undo deployment skx --to-revision=1deployment.extensions/skx rolled backcurl 10.96.174.199
songkaixiong | test-web | | v1
用label控制Pod的位置给node03打上一个标签[root@master ~]# kubectl label nodes node03 disk=ssdnode/node03 labeled指定查看node03标签：[root@master ~]# kubectl get nodes --show-labels | grep node03node03 Ready
[root@master ~]# kubectl delete -f skx-svc.yaml service "skx-svc" deleted
修改skx1.yaml配置文件：[root@master ~]# vim skx1.yaml kind: DeploymentapiVersion: extensions/v1beta1metadata:name: skxspec:revisionHistoryLimit: 10replicas: 3template:metadata:labels:app: skx_serverspec:containers:
name: 192.168.1.10:5000/httpd:v1ports:
containerPort: 80nodeSelector: //添加节点选择器disk: ssd //和标签内容一致[root@master ~]# kubectl apply -f skx1.yaml deployment.extensions/skx created三台都在node03上运行：[root@master ~]# kubectl get pod -o wideNAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATESskx-55c4dc6dbc-7ztl9 1/1 Running 0 73s 10.244.2.27 node03
删除标签：查看node03的标签：[root@master ~]# kubectl get nodes --show-labels node03NAME STATUS ROLES AGE VERSION LABELSnode03 Ready
删除资源：[root@master ~]# kubectl delete deployments. skx deployment.extensions "skx" deleted重新生成：[root@master ~]# kubectl apply -f skx1.yaml deployment.extensions/skx unchanged会找不到，起不来：[root@master ~]# kubectl get pod -o wideNAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATESskx-55c4dc6dbc-8rpl6 0/1 Pending 0 11s
[root@master ~]# kubectl get pod -n kube-system NAME READY STATUS RESTARTS AGEcoredns-5c98db65d4-52cdm 1/1 Running 3 5d17hcoredns-5c98db65d4-sl96w 1/1 Running 4 5d17hetcd-master 1/1 Running 3 5d17hkube-apiserver-master 1/1 Running 3 5d17hkube-controller-manager-master 1/1 Running 3 5d17hkube-flannel-ds-amd64-9vnsc 1/1 Running 4 5d17hkube-flannel-ds-amd64-tdzrm 1/1 Running 2 5d17hkube-flannel-ds-amd64-tvl2q 1/1 Running 5 5d17hkube-proxy-492jr 1/1 Running 2 5d17hkube-proxy-gccnb 1/1 Running 3 5d17hkube-proxy-klznh 1/1 Running 2 5d17hkube-scheduler-master 1/1 Running 4 5d17h
查看master日志：[root@master ~]# kubectl logs -n kube-system kube-scheduler-master 查看详细描述信息[root@master ~]# kubectl describe pod skx-55c4dc6dbc-8rpl6查看日志[root@master ~]# kubectl logs -n kube-system kube-scheduler-master 查看kubectl日志[root@master ~]# less /var/log/messages | grep kubelet
版权声明：本文内容由网络用户投稿，版权归原作者所有，本站不拥有其著作权，亦不承担相应法律责任。如果您发现本站中有涉嫌抄袭或描述失实的内容，请联系我们jiasou666@gmail.com 处理，核实后本网站将在24小时内删除侵权内容。
相关文章
发表评论
暂时没有评论，来抢沙发吧~