Epic Goal

• Upstream work for Multi dimensional autoscaling
• Operator to use both vertical and horizontal scaling
• Use the logic in VPA and HPA

Why is this important?

• VPA and HPA do not necessarily work together. Vertical (Memory scaling) Horizontal (CPU scaling).
• Others have this functionality already
• Contribute to upstream work (API, Enhancement, code, etc)

Scenarios

1. Using this operator, memory pressure on a node would cause work to be shed to additional nodes based on the TBD memory metric
2. Using this operator, CPU load on a node would cause work to be shed to additional nodes based on the TBD CPU metric

Acceptance Criteria

• CI - MUST be running successfully with tests automated
• Release Technical Enablement - Provide necessary release enablement details and documents.
• Usable controller to scale vertically and horizontally on different metrics
  • not thrashing cluster
• Follow up Epic (Phase 2) will be created to productize and get the operator within Operator Hub

Dependencies (internal and external)

1. TBD

Previous Work (Optional):

1. Others have this functionality already

Open questions:

1. Which metrics to monitor for scaling?
2. Can this operator be implemented as  a "composition" of current VPA, HPA operators?

Done Checklist

• CI - CI is running, tests are automated and merged.
• Release Enablement <link to Feature Enablement Presentation>
• DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
• DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
• DEV - Downstream build attached to advisory: <link to errata>
• QE - Test plans in Polarion: <link or reference to Polarion>
• QE - Automated tests merged: <link or reference to automated tests>
• DOC - Downstream documentation merged: <link to meaningful PR>