Uploaded image for project: 'OpenShift Request For Enhancement'
  1. OpenShift Request For Enhancement
  2. RFE-8791

Gateway API: Ability to configure nodeSelector/tolerations in GatewayClass

XMLWordPrintable

    • None
    • Product / Portfolio Work
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      1. Proposed title of this feature request

      Ability to configure nodeSelector/tolerations in GatewayClass 

      2. What is the nature and description of the request?

      Currently there are no abilities to configure nodeSelector/tolerations in GatewayClass

      As a result pods deployed in openshift-ingress namespace cannot be moved on infra nodes such:

      • istiod
      • kube-auth-proxy
      • istio-proxy

      3. Why does the customer need this? (List the business requirements here)

      Many AI customers have only tainted worker GPU nodes to prevent the scheduling of non AI business related workload in those expensive nodes. They don't have any other worker node types. They expect the OCP platform component to run in infra node in order to:

      • save subscriptions from pure platform related workload
      • save space in their expensives GPU nodes 

      4. List any affected packages or components.

      Gateway API : GatewayClass

              mcurry@redhat.com Marc Curry
              laurent.tourreau Laurent TOURREAU
              None
              Votes:
              1 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                None
                None