-
Feature
-
Resolution: Obsolete
-
Major
-
None
-
None
-
None
-
False
-
False
-
?
-
No
-
?
-
?
-
?
-
0% To Do, 0% In Progress, 100% Done
-
Undefined
Goal
Enable Operator authors to add advanced features through easy access to reusable APIs or libraries.
Why is this important
Continue to differentiate our OCP platform with our partner ecosystem to help Red Hat and partners’ Operator teams to develop advanced capabilities.
To help achieve higher Operator maturity, we want to achieve this by providing more reusable implementations/libraries so users can easily opt-in (potentially through custom project scaffolding) with less development effort and in a consistent manner.
Thereby, the Operator SDK is:
- not just perceived as a "day 1" tool to get Operator authors off the ground
- but instead, a powerful tool for its easy access to the new reusable features during the full development cycle
so users can continue to learn best practices and develop advanced capabilities with the SDK, and ultimately, the Operator maturity increases via the Operator SDK.
Deliverables
- auto-pruning deleting Operator created objects
- editing and exposing custom metrics
- auto-scaling per metrics
- with VPA:
- For Operator resource limits
- with HPA:
- For scaling Operand replica
- with VPA:
- auto-tuning per metrics
- is related to
-
OPECO-1895 Auto-pruning of Objects created by layered products via Operators
- Closed
- is triggered by
-
OCPPLAN-6823 Make OpenShift Operators more mature
- New