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

Request to add “kubernetes workload” scaler/trigger in CMA

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Undefined Undefined
    • None
    • None
    • Autoscaling
    • None
    • Quality / Stability / Reliability
    • None
    • False
    • Hide

      None

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

      1. Proposed title of this feature requestRequest to add “kubernetes workload” scaler/trigger in CMA
      2. What is the nature and description of the request? Morgans's customers utilizes CMA and the only trigger/scaler which is missing in CMA that they want to use is, “kubernetes-workload”
      Kubernetes-workload: Scale applications based on the count of running pods that match the given selector.
      Ref doc: https://keda.sh/docs/2.17/scalers/kubernetes-workload/
      3. Why does the customer need this? (List the business requirements here)Triggers/scalers CMA support today is “Prometheus,CPU,memory,Apache Kafka and Cron” as opposed to 74 scalers supported in upstream KEDA
      4. List any affected packages or components.

              rh-ee-smodeel Subin M
              priysing@redhat.com Priyanka Singh
              None
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                None
                None