A common issue in Kubernetes is encountering problems with a Job that fails to finish, run, or even get scheduled.
Before diving into troubleshooting, let's establish some common reasons why a Kubernetes Job might not be running:
1️⃣ Lack of Permissions – The Job is not able to execute due to insufficient privileges.
2️⃣ Scheduling Issues – The Job cannot be scheduled due to:
3️⃣ Other Unexpected Reasons – Additional issues that require further investigation.
To find a feasible solution, we first need to understand the problem.
In our ArgoCD, we are seeing something like:
The message is: waiting for completion of hook batch/Job/passbolt-development-job-create-gpg-keys
Since we are trying to install Passbolt - an open source password manager - there is a concept of gpg keys, in which every password is encrypted by Passbolt with a gpg keys. This is a combination of an private key-public key, ensuring that only authorized users can decrypt stored passwords.
You can eiter provide these gpg keys as Secret yourself, or you let Passbolt create it for you.
In this troubleshoot guide, I continue for opting to let Passbolt create it for us.
”I WANT THE JOB TO WORK LIKE IT SHOULD - SOME PROGRAMMING GOD”
To further understand the problem, we will do a deep dive in the Troubleshoot section.