Issues with Cluster Autoscaler when custom `defaultNodeSelector` is defined

Solution Verified - Updated -

Issue

  • The AWS nodes are not been triggered with autoscaling when custom defaultNodeSelector is configured.
  • Pods are not able to schedule in autoscaled nodes.

Environment

  • Red Hat OpenShift Container Platform 3.11
  • Amazon Web Services

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