-
Epic
-
Resolution: Done
-
Major
-
ACM 2.8.0
Feature Overview
The labels set on a ManagedCluster should be propagated to ArgoCD, so they can be used in ArgoCD to e.g. select different Kustomize overlays in the same ApplicationSet.
Goals
This Section: Provide high-level goal statement, providing user context
and expected user outcome(s) for this feature
- Propagate labels set on a ManagedCluster to secrets created for ArgoCD
Requirements
This Section: A list of specific needs or objectives that a Feature must
deliver to satisfy the Feature.. Some requirements will be flagged as MVP.
If an MVP gets shifted, the feature shifts. If a non MVP requirement slips,
it does not shift the feature.
| Requirement | Notes | isMvp? |
|---|---|---|
| CI - MUST be running successfully with test automation | This is a requirement for ALL features. |
YES |
| Release Technical Enablement | Provide necessary release enablement details and documents. |
YES |
(Optional) Use Cases
This Section:
- Select different Kustomize overlays in the same `ApplicationSet` by using a label like `env`, which can be queried in the `ApplicationSet`.
Questions to answer
- ...
Out of Scope
- …
Background, and strategic fit
This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?
Assumptions
- ...
Customer Considerations
- ...
Documentation Considerations
Questions to be addressed:
- What educational or reference material (docs) is required to support this
product feature? For users/admins? Other functions (security officers, etc)? - Does this feature have a doc impact?
- New Content, Updates to existing content, Release Note, or No Doc Impact
- If unsure and no Technical Writer is available, please contact Content
Strategy. - What concepts do customers need to understand to be successful in
[action]? - How do we expect customers will use the feature? For what purpose(s)?
- What reference material might a customer want/need to complete [action]?
- Is there source material that can be used as reference for the Technical
Writer in writing the content? If yes, please link if available. - What is the doc impact (New Content, Updates to existing content, or
Release Note)?
ACM Epic Done Checklist
See presentation and details.
Update with "Y" if Epic meets the requirement, "N" if it does not, or "N/A" if not applicable.
- Y FIPS Readiness
- Y Works in Disconnected
- Y Global Proxy Support
- Y Installable to Infrastructure Nodes
- Y No impacts to Performance and Scalability
- Y Backup and Restorable
- is related to
-
-
- Closed
-
- links to
