-
Epic
-
Resolution: Done
-
Major
-
None
-
None
-
Spike: helm implementation approach
-
S
-
False
-
-
False
-
-
Done
-
RHIDP-6100 - Orchestrator flavor in helm chart
-
QE Needed, Docs Needed, TE Needed, Customer Facing, PX Needed
-
0% To Do, 0% In Progress, 100% Done
-
Release Note Not Required
-
-
- Evaluate implementing as a Helm subchart vs values-based configuration
- Subchart pros: cleaner separation, independent versioning
- Subchart cons: more complex maintenance, potential version conflicts
- Values-based pros: simpler implementation, unified versioning
- Values-based cons: less flexibility, potential naming conflicts
- Leaning towards subchart, because 3rd parties can replicate this approach easier
- Do so many layers of helm charts, subcharts a good practice?
- Forking upstream chart vs contributing changes to upstream chart vs removing the upstream dependency
- E.g. extraFiles, extraContainer, ...
- Maybe only RHDH core chart and one subchart per flavor
