Uploaded image for project: 'OpenShift GitOps'
  1. OpenShift GitOps
  2. GITOPS-4189

Auto-Scaling Shards to Handle Workload Spikes

XMLWordPrintable

    • Icon: Epic Epic
    • Resolution: Unresolved
    • Icon: Minor Minor
    • None
    • None
    • None
    • Auto-Scaling Shards to Handle Workload Spikes
    • False
    • Hide

      None

      Show
      None
    • False
    • SECFLOWOTL-88 - Augment Argo-CD sharding capabilities by implementing additional sharding algorithms

      Story (Required)

      As an Argo-CD administrator, I want the sharding algorithm to automatically scale the number of shards based on workload spikes. The algorithm

      Background (Required)

      This can be performed by using the horizontalPodAutoscaler (hpa) feature.

      Out of scope

      Do not try to implement the autoscaling at the controller level, but rather be sure that the application-controller will react properly in case of automatica scaling

      Approach (Required)

      Enable hpa and see what are the impact. Add the hpa to the operator manifest and add configuration parameter to enable it on user's will.

      Dependencies

      GITOPSRVCE-613

      Acceptance Criteria (Mandatory)

      When the CPU load (default hpa) of the pod becomes too high, the hpa should automatically increase the number of replicas of the StatefulSet or the Deployment and the the application-controller should notice it.

      INVEST Checklist

      Dependencies identified

      Blockers noted and expected delivery timelines set

      Design is implementable

      Acceptance criteria agreed upon

      Story estimated

      Legend

      Unknown

      Verified

      Unsatisfied

      Done Checklist

      • Code is completed, reviewed, documented and checked in
      • Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
      • Continuous Delivery pipeline(s) is able to proceed with new code included
      • Customer facing documentation, API docs etc. are produced/updated, reviewed and published
      • Acceptance criteria are met

              Unassigned Unassigned
              abenaiss Akram Ben Aissi
              GitOps
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: