Vulnerability-Advisor-sas-apiserver pods are stuck in Init status
Troubleshoot the Vulnerability-Advisor-sas-apiserver pods are stuck in Init status issue.
Curl failed to verify the legitimacy of the server and therefore could not establish a secure connection to it.
For upgrade on FP4 to FP5, there's still one pod in Init
vulnerability-advisor-sas-apiserver-855bdb64c7-l9vxb 0/4 Init:0/1 0 18h
vulnerability-advisor-sas-apiserver pod getting stuck is due to OCP on cleaning up the pod.
Resolving the issue
It does not obstruct/create any loss of functionality and as a workaround, delete the deployment which should resolve it.
There has been a configMap change in
vulnerability-advisor-sas-apiserver-init from FP4 to FP5.
After deleting the configmap and restarting the pod it came back to running state. This is only seen in upgrade scenario.