+++ This bug was initially created as a clone of Bug #1783445 +++ Description of problem: If etcd is backing up a snapshot of the database, it behooves to copy the static pod resources of kube-apiserver at the time of backup. When we restore, the revision of the static pod resources must match with the restored database. Version-Release number of selected component (if applicable): 4.3 How reproducible: Encrypted etcd failed without matching configuration. Steps to Reproduce: 1. Take an etcd snapshot of encrypted configuration. 2. Restore it on all masters (esp. if the revision of apiserver changed) Actual results: kube-apiserver doesn't fully recover. Expected results: The cluster recovers and becomes fully functional. Additional info: Related to discussion in Bug https://bugzilla.redhat.com/show_bug.cgi?id=1776811
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:0062