当前位置:  首页>> 技术小册>> Kubernets合辑5-Pod控制器

daemonset的升级方式和deployment一致

  1. [root@hdss7-21 ~]# kubectl rollout history daemonset proxy-daemonset -n app
  2. REVISION CHANGE-CAUSE
  3. 1 kubectl apply --filename=http://k8s-yaml.od.com/base_resource/daemonset/proxy-v1.12.yaml --record=true
  4. [root@hdss7-21 ~]# kubectl apply -f http://k8s-yaml.od.com/base_resource/daemonset/proxy-v1.13.yaml --record
  5. [root@hdss7-21 ~]# kubectl rollout history daemonset proxy-daemonset -n app
  6. daemonset.extensions/proxy-daemonset
  7. REVISION CHANGE-CAUSE
  8. 1 kubectl apply --filename=http://k8s-yaml.od.com/base_resource/daemonset/proxy-v1.12.yaml --record=true
  9. 2 kubectl apply --filename=http://k8s-yaml.od.com/base_resource/daemonset/proxy-v1.13.yaml --record=true
  10. [root@hdss7-21 ~]# kubectl get pod -n app -l tier=proxy -L version
  11. NAME READY STATUS RESTARTS AGE VERSION
  12. proxy-daemonset-7wr4f 1/1 Running 0 119s v1.13
  13. proxy-daemonset-clhqk 1/1 Running 0 2m11s v1.13

该分类下的相关小册推荐: