-
Epic
-
Resolution: Won't Do
-
Major
-
None
-
Cluster templates back-end implementation
-
False
-
False
-
Green
-
To Do
-
ACM-4 - Cluster Templates
-
0% To Do, 0% In Progress, 100% Done
Epic Goal
Architect and build a back-end component that will enable a cluster templates feature
Feature spec: https://docs.google.com/document/d/1Q7YNPgaw8Z9S9abDdnOlY0QuUP72YphnPib-WhJrj_4/edit#
Input to Docs:
This epic will provide the developer/devops persona with an ability to self service clusters in a way that the hub cluster administrator is comfortable with.
The hub cluster admin defines the a set of templates and chooses which aspects of the template might be parametrizable by the user and under what conditions.
The developer/devops persona is than able to instantiate these templates while having absolute minimum permissions on the hub.
Technically, all the heavy lifting is done by ArgoCD and ACM's policy framework. This epic provides the wiring, orchestration and additional guardrails (in form of quotas).
More details in the feature spec and docs story
Why is this important?
- Improve the OpenShift installation experience
- Allow admins/SREs to pre-define cluster configurations for cluster users
- Enable the simplification and usability of the create cluster UI, create cluster wizard is cumbersome after going through it a few times.
Scenarios
- Admin can define a template for a cluster using Helm
- Admin can store templates in Git and deliver them to a cluster via GitOps
- A second user can instatiate a Helm release for the defined template (Helm chart) to create a cluster
Acceptance Criteria
- CI - MUST be running successfully with tests automated
- Release Technical Enablement - Provide necessary release enablement details and documents.
- ...
Dependencies (internal and external)
- ...
Previous Work (Optional):
- …
Open questions::
- …
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>