RFE: Add readinessProbe to Deployment manifest

[AaronJaegerVA]

cloud-credential-operator/manifests/03-deployment.yaml

Line 34 in 6a880b4

containers:

I have encountered situations where the CCO controller Pod is not functioning and regularly crashing, but due to no readinessProbe, looks fine on the surface. This has happened with the CCO in Mint Mode while using an AWS Provider when the kube-system/aws-creds information becomes invalid due to IAM access/secret keys being deactivated after a rotation.

I have previously seen messages in the logs indicating AWS permission issues, but lately the CCO container logs are silent. The only symptom was never-ending messages like these in the CCO Pod's kube-rbac-proxy container's logs:

I0519 19:48:43.671759 1 log.go:245] http: proxy error: dial tcp 127.0.0.1:2112: connect: connection refused

[openshift-bot]

Issues go stale after 90d of inactivity.

Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.

If this issue is safe to close now please do so with /close.

/lifecycle stale

[AaronJaegerVA]

/lifecycle frozen