Skip to main content

Pods stuck in Pending

Common causes: no matching nodes (check taints and tolerations), insufficient resources, or the NodePool not creating nodes. If nodes aren’t being provisioned, check Karpenter:

Image pull errors

e6-operator not starting

NamespaceConfig or QueryRouter stuck in Error

Pod Identity issues

LoadBalancer not getting an external IP

Monitoring not sending data

Support

For deployment assistance, contact e6data support at [email protected], or reach your e6data account team for your dedicated support channel.

See also

Last modified on September 29, 2026