auth-server-key-rotation job fails when there is any auth-server pod in non-RUNNING Status

**Describe the bug**
We are using cloudtools to rotate the jwks keys every 2 days. The job fails when there are any auth-server pod in non-running status, for example in COMPLETED, FAILED or CrashLoopBackOff status.

**To Reproduce**
Steps to reproduce the behavior:
1. Try to update the auth-server deployment to use a non-existing image like `testimage`
2. The new auth-server pod will go into CrashLoopBackOff status.
3. Run the cronjob for auth-server-key-rotation
4. The pod does not complete and fails.

**Expected behavior**
The Key rotation job should work and not fail if it find any auth-server in non RUNNING Status.