When security pods remain in Pending (unscheduled) state the most frequent cause is that the pod images cannot be pulled because the Resource Registry ConfigMap is wrongly set (for example, incorrect image-registry path or secret). IBM CP4BA installation troubleshooting guides explicitly direct administrators to verify and, if necessary, correct the Resource Registry before further action; once the registry is fixed, the scheduler can place the security pods.

B. Re-queueing by the reconcile loop will not fix a mis-configured registry; pods will stay Pending.

C. CPU/memory problems leave pods Pending with “insufficient resources”, not specifically the security pods issue called out in CP4BA docs.

D. JMS queues are unrelated to pod scheduling or image pull operations.

1. IBM Cloud Pak for Business Automation 22.0.1 Documentation – “Troubleshooting installation > Security pods not scheduled”

steps 1-3 (doc ID: cp4a-trbl-sec-pods)

2. IBM Cloud Pak Foundational Services 3.22 – “Offline install > Verifying the Resource Registry ConfigMap”

paragraph 2–3

3. Redbook: Malhoit et al.

“IBM Cloud Pak for Business Automation Installation and Deployment”

SG24-8482-00

Ch.14

p. 318-319

4. IBM Support Technote: “Security pods remain in Pending state after CP4BA install” (TS009908)

section ‘Cause’ para 1 and ‘Resolving the problem’ step 1