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

Add supportability for GCP for Openshift Keda.

XMLWordPrintable

    • Icon: Feature Request Feature Request
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • None
    • Autoscaling
    • 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
      GCP Storage and Pub/Sub triggers for scaling deployment.

      2. What is the nature and description of the request?
      We are currently using the Custom Metrics AutoScaler operator, version v2.14.1-467. We've successfully tested CPU, Memory, Cron, and Prometheus triggers, and they are working as expected. However, when attempting to use Google Cloud Platform (GCP) triggers for GCS bucket and Pub/Sub as per documented in Keda official docsiteĀ 
      https://keda.sh/docs/2.12/scalers/gcp-storage/
      We encountered errors in the operator pod logs. Also the Rehat documentation indicates that the custom metrics autoscaler currently supports only Prometheus, CPU, memory, Apache Kafka, and cron triggers

      3. Why does the customer need this? (List the business requirements here)
      We require this feature to scale Kubernetes workloads based on the count of objects in a given Google Cloud Storage (GCS) bucket and Pub/Sub trigger to scale based on any metrics from our Pub/Sub subscription or topic, such as number of messages or oldest unacked message age, etc.

      4. List any affected packages or components.

      NA

              rh-ee-smodeel Subin M
              rhn-support-udeshmuk Uttkarsh Deshmukh
              None
              Votes:
              0 Vote for this issue
              Watchers:
              1 Start watching this issue

                Created:
                Updated:
                None
                None