Ansible Automation Platform gateway proxy pods fail under OpenShift LimitRange after upgrade (CPU limit 256)

Solution Verified - Updated -

Issue

  • After upgrading to Ansible Automation Platform 2.6 on OpenShift, the platform gateway becomes unavailable
  • Gateway or UI access returns HTTP 503 or similar errors
  • Gateway pods remain Pending, fail admission, or do not become Ready
  • The gateway proxy container is configured with a CPU limit of 256 cores, which exceeds the namespace LimitRange maximum CPU
  • Typical LimitRange / admission failure pattern:

    <Forbidden / LimitRange admission error stating maximum cpu usage per Container is N, but limit is 256>
    

Environment

  • Red Hat Ansible Automation Platform 2.6 (operator-based install)
    • Namespace-scoped bundle: aap-operator.v2.6.0-0.1783986120
    • Cluster-scoped bundle: aap-operator.v2.6.0-0.1783986130
  • Red Hat Ansible Automation Platform 2.7 (operator-based install)
  • Namespace has a LimitRange (or ResourceQuota) with a per-container CPU maximum lower than 256

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content