SUMMARY Is some k8s deployments, etcd cluster (used by multicloud-k8s subchart) cannot start due to startup script's ping failing in liveness check timeout time. OS / ENVIRONMENT Kubernetes version: Client Version: version.Info{Major: "1" , Minor: "15" , GitVersion: "v1.15.11" , GitCommit: "d94a81c724ea8e1ccc9002d89b7fe81d58f89ede" , GitTreeState: "clean" , BuildDate: "2020-03-12T21:08:59Z" , GoVersion: "go1.12.17" , Compiler : "gc" , Platform: "linux/amd64" } Server Version: version.Info{Major: "1" , Minor: "15" , GitVersion: "v1.15.9" , GitCommit: "2e808b7cb054ee242b68e62455323aa783991f03" , GitTreeState: "clean" , BuildDate: "2020-01-18T23:24:23Z" , GoVersion: "go1.12.12" , Compiler : "gc" , Platform: "linux/amd64" } Helm version: Client: &version.Version{SemVer: "v2.16.6" , GitCommit: "dd2e5695da88625b190e6b22e9542550ab503a47" , GitTreeState: "clean" } Server: &version.Version{SemVer: "v2.16.6" , GitCommit: "dd2e5695da88625b190e6b22e9542550ab503a47" , GitTreeState: "clean" } Kubernetes mode of installation: offline-installer CNI Used for Kubernetes: canal type of installation: 1 control, 3 workers OOM VERSION frankfurt, guilin, master CONFIGURATION not needed STEPS TO REPRODUCE not needed EXPECTED RESULTS not needed ACTUAL RESULTS not needed