Update about DUPLEX:
After the system was stable (all pods propperly running) and retrying the sanity test, same behavior was detected. PODs are restaring:
kube-system ingress-658v7 1/1 Running 19 5h5m kube-system ingress-error-pages-59766f99fd-nnb5p 1/1 Running 2 5h5m kube-system ingress-error-pages-59766f99fd-xfb7m 1/1 Running 6 5h5m kube-system ingress-wt86d 1/1 Running 3 5h5m kube-system kube-apiserver-controller-0 1/1 Running 7 5h57m kube-system kube-apiserver-controller-1 1/1 Running 4 5h24m kube-system kube-controller-manager-controller-0 1/1 Running 16 5h57m kube-system kube-controller-manager-controller-1 1/1 Running 15 5h24m kube-system kube-proxy-9255h 1/1 Running 1 5h58m kube-system kube-proxy-n25lg 1/1 Running 2 5h24m kube-system kube-scheduler-controller-0 1/1 Running 17 5h57m kube-system kube-scheduler-controller-1 1/1 Running 15 5h24m kube-system tiller-deploy-d87d7bd75-p7k85 0/1 CrashLoopBackOff 30 5h54m
Update about DUPLEX:
After the system was stable (all pods propperly running) and retrying the sanity test, same behavior was detected. PODs are restaring:
kube-system ingress-658v7 1/1 Running 19 5h5m error-pages- 59766f99fd- nnb5p 1/1 Running 2 5h5m error-pages- 59766f99fd- xfb7m 1/1 Running 6 5h5m controller- 0 1/1 Running 7 5h57m controller- 1 1/1 Running 4 5h24m -manager- controller- 0 1/1 Running 16 5h57m -manager- controller- 1 1/1 Running 15 5h24m controller- 0 1/1 Running 17 5h57m controller- 1 1/1 Running 15 5h24m deploy- d87d7bd75- p7k85 0/1 CrashLoopBackOff 30 5h54m
kube-system ingress-
kube-system ingress-
kube-system ingress-wt86d 1/1 Running 3 5h5m
kube-system kube-apiserver-
kube-system kube-apiserver-
kube-system kube-controller
kube-system kube-controller
kube-system kube-proxy-9255h 1/1 Running 1 5h58m
kube-system kube-proxy-n25lg 1/1 Running 2 5h24m
kube-system kube-scheduler-
kube-system kube-scheduler-
kube-system tiller-