<p>Cluster consists of one master and one worker node. If the master is down and worker is restarted no workloads (deployments) are started on boot. How and if it is possible to make worker resume last state without master?</p>

<p>Kubernetes 1.18.3</p>

<p>On worker node are installed: kubelet, kubectl, kubeadm</p>

Jonas
<p>Ideally you should have more than one(typically a odd number like 3 or 5) node serving as master and accessible from worker nodes via a LoadBalancer.</p>

<p>The state is stored in ETCD which is accessed by worker nodes via the API Server. So without master nodes running there is no way for workers to know the desired state. </p>

<p>Although it's not recommended you but can use <a href="https://kubernetes.io/docs/tasks/configure-pod-container/static-pod/" rel="nofollow noreferrer">static pod</a> as potential solution here.Static Pods are managed directly by the kubelet daemon on a specific node, without the API server observing them.Unlike Pods that are managed by the control plane (for example, a Deployment ), instead the kubelet watches each static Pod (and restarts it if it crashes).</p>

<p>The caveat of using static pod is since those pods are not dependent on API Server Hence static Pods cannot be managed with kubectl or other Kubernetes API clients.</p>
