IBM Support

API Connect Gateway Pod Stuck in Pending State on OpenShift

Troubleshooting


Problem

The API Connect Gateway pod remains in a Pending state on OpenShift. Running the following command:
oc describe pod/<gateway-pod-name> -n <project_where_APIC_is_deployed>
reveals scheduling issues:
Warning  FailedScheduling  27m (x28 over 69m)  default-scheduler  0/11 nodes are available: 
    2 Insufficient memory, 
    3 node(s) had untolerated taint {node-role.kubernetes.io/master: }, 
    6 node(s) had untolerated taint {node.cloudprovider.kubernetes.io/uninitialized: true}. 

preemption: 0/11 nodes are available: 
    2 No preemption victims found for incoming pod, 
    9 Preemption is not helpful for scheduling.

Document Location

Worldwide

[{"Type":"MASTER","Line of Business":{"code":"LOB77","label":"Automation Platform"},"Business Unit":{"code":"BU048","label":"IBM Software"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"ARM Category":[{"code":"a8mKe000000CaZVIA0","label":"API Connect-\u003EAPIC Gateway"}],"ARM Case Number":"TS018460863","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0.5;and future releases"}]

Log InLog in to view more of this document

This document has the abstract of a technical article that is available to authorized users once you have logged on. Please use Log in button above to access the full document. After log in, if you do not have the right authorization for this document, there will be instructions on what to do next.

Document Information

Modified date:
10 March 2025

UID

ibm17185198

Page Feedback