One of the kube-apiserver pods had a fatal startup error but the operator never entered a degraded state.

~~~~~~

informer-sync check failed: readyz [-]informer-sync failed: 2 informers not started yet: [*v1.Secret *v1.ConfigMap]

"failed to decrypt data" err="no matching key was found for the provided AES transformer"

failed to list *core.ConfigMap: unable to transform key "/kubernetes.io/configmaps/..."

failed to list *core.Secret: unable to transform key "/kubernetes.io/secrets/..."apiserver was unable to write a JSON response: http: Handler timeout 

~~~

kube-apiserver   4.16.37   True   True   False   2y143d   NodeInstallerProgressing: 3 nodes are at revision 642; 0 nodes have achieved new revision 648 

~~~ 
$ oc get pods kube-apiserver-ip-10-128-40-151.ca-central-1.compute.internal
NAME                                                            READY   STATUS    RESTARTS   AGE
kube-apiserver-ip-10-128-40-151.ca-central-1.compute.internal   4/5     Running   0          40h        45d
~~~

  seen on 4.16.37

    did not reproduce

  1. encrypt etcd during cluster deployment
  2. delete a resource but entry is not removed from etcd

Resources is deleted and the subsequent entry is not removed from etcd.
kube-apiserver pods no longer functional due to `no matching key was found for the provided AES transformer' KAS operator reports healthy and stuck in a progressing state.    

Resources is deleted and the subsequent entry is not removed from etcd. kube-apiserver fails to start and operator enters a degraded state.    

KCS to unblock the issue https://access.redhat.com/solutions/6769801