k8s CICD部署脚本
#!/bin/bash
sj=$(date +"%Y%m%d-%H%M%S")
docker build -t 172.17.250.186/asset-app/user-server:"${sj}" /mnt/dockerfile/asset-app/user-server
docker push 172.17.250.186/asset-app/user-server:"${sj}"
docker build -t 172.17.250.186/asset-app/sms-server:"${sj}" /mnt/dockerfile/asset-app/sms-server
docker push 172.17.250.186/asset-app/sms-server:"${sj}"
docker build -t 172.17.250.186/asset-app/app-product:"${sj}" /mnt/dockerfile/asset-app/business-product
docker push 172.17.250.186/asset-app/app-product:"${sj}"
docker build -t 172.17.250.186/asset-app/app-discover:"${sj}" /mnt/dockerfile/asset-app/business-discover
docker push 172.17.250.186/asset-app/app-discover:"${sj}"
docker build -t 172.17.250.186/asset-app/app-home:"${sj}" /mnt/dockerfile/asset-app/business-home
docker push 172.17.250.186/asset-app/app-home:"${sj}"
docker build -t 172.17.250.186/asset-app/app-h5:"${sj}" /mnt/dockerfile/asset-app/h5
docker push 172.17.250.186/asset-app/app-h5:"${sj}"
docker build -t 172.17.250.186/asset-app/seal-sign:"${sj}" /mnt/dockerfile/asset-app/seal-sign
docker push 172.17.250.186/asset-app/seal-sign:"${sj}"
/opt/kubernetes/bin/kubectl delete -f /root/yaml-k8s/
sed -i "s#$(egrep 172.17.250.186 /root/yaml-k8s/app-deploy-discover.yaml)# image: 172.17.250.186/asset-app/app-discover:${sj}#g" /root/yaml-k8s/app-deploy-discover.yaml
sed -i "s#$(egrep 172.17.250.186 /root/yaml-k8s/app-deploy-home.yaml)# image: 172.17.250.186/asset-app/app-home:${sj}#g" /root/yaml-k8s/app-deploy-home.yaml
sed -i "s#$(egrep 172.17.250.186 /root/yaml-k8s/app-deploy-product.yaml)# image: 172.17.250.186/asset-app/app-product:${sj}#g" /root/yaml-k8s/app-deploy-product.yaml
sed -i "s#$(egrep 172.17.250.186 /root/yaml-k8s/app-deploy-sms.yaml)# image: 172.17.250.186/asset-app/sms-server:${sj}#g" /root/yaml-k8s/app-deploy-sms.yaml
sed -i "s#$(egrep 172.17.250.186 /root/yaml-k8s/app-deploy-user.yaml)# image: 172.17.250.186/asset-app/user-server:${sj}#g" /root/yaml-k8s/app-deploy-user.yaml
sed -i "s#$(egrep 172.17.250.186 /root/yaml-k8s/app-h5.yaml)# image: 172.17.250.186/asset-app/app-h5:${sj}#g" /root/yaml-k8s/app-h5.yaml
sed -i "s#$(egrep 172.17.250.186 /root/yaml-k8s/seal-sign.yaml)# image: 172.17.250.186/asset-app/seal-sign:${sj}#g" /root/yaml-k8s/seal-sign.yaml
/opt/kubernetes/bin/kubectl apply -f /root/yaml-k8s/
相关文章
- K8S学习圣经:大白话说K8S底层原理,14W字实现K8S自由
- k8s中label和label selector的基本概念及使用方法
- k8s集群中部署prometheus server
- k8s集群中部署和访问Dashboard服务
- K8S原理剖析:存储原理剖析和实践
- 32 张配图详解 K8S 1.24 高可用部署,保姆级详细版
- K8s 集群 LIST 请求源码分析、性能评估与大规模基础服务部署调优
- kustomize (五) 使用vars将 k8s runtime 数据注入容器
- 微服务容器化迁移——在K8s中部署Spring Cloud
- 再次登顶 GitHub,阿里大牛用 758 页讲清微服务 K8S 响应式的文案,真的太香了
- 部署 Spring Boot 应用到 K8S 教程
- 谷粒商城K8s部署中间件(二十八)
- k8s源码分析3-kubectl命令行设置7大命令分组
- 为k8s预留系统资源
- istio在k8s中的部署
- k8s-部署Dashboard (仪表板)
- k8s服务端二进制部署-kubectl
- 线上 K8s 集群性能评估、基础服务部署调优
- K8s 节点断开连接后,本在运行的 Pod 会如何?
- k8s SLUB: Unable to allocate memory on node -1 错误
- k8s部署rocketmq 双主
- k8s 准入控制
- k8s pod 内存 所以判断container_memory_working_set_bytes会比container_memory_usage_bytes更为准确
- k8s 证书 ca apiserver etcd kube-proxy kubelet-clent
- k8s中YAML文件书写格式
- k8s部署nacos 一直报错No DataSource set(k8s踩坑--警示-操作失误导致)
- k8s高可用部署后续:SLB
- kubernetes专题二:k8s架构