kubernetes log roll test
Others
2019-12-18 18:51:35
views: null
kubernetes log roll test
| The initial pod |
ms-zipkin-deployment-5949c78884-4x5h7 |
kubectl logs ms-zipkin-deployment-5949c78884-4x5h7 --namespace=ecs2 |
Full log |
| Manipulation of the container to collapse and automatic rebuild container k8s |
ms-zipkin-deployment-5949c78884-4x5h7 |
kubectl logs ms-zipkin-deployment-5949c78884-4x5h7 --namespace=ecs2 --previous |
Previous version of the container vessel operation command log collapse + |
| Manual rollback pod |
ms-zipkin-deployment-54f87bb4dc-hk6v8 |
kubectl logs ms-zipkin-deployment-54f87bb4dc-hk6v8 --namespace=ecs2 --previous |
Suggesting no history pod |
in conclusion
- Automatic restart after the container hang up, pod will not re-create, podname will not change, k8s retain the log information last hang container
- Manually redeploy, podname changes to the log information can not be obtained when the last vessel crash
Origin www.cnblogs.com/yechen2019/p/12061199.html