-
Feature
-
Resolution: Done
-
Critical
-
None
Feature Overview
De-coupling the Open Cluster Management Policy framework from the OCM management control plane; enabling Policies to be able to be deployed to a given cluster via any desired "transport" mechanism.
Improve integrations with ArgoCD; and leverage ArgoCD for its capabilities to fill in feature gaps that will be unavailable in the standalone deployment model (that are normally available through the current hub deployment model).
Goals
This Section: Provide high-level goal statement, providing user context
and expected user outcome(s) for this feature
- Allow for Configuration/Certificate/OperatorPolicies to be able to be defined directly to a cluster without going through the hub cluster via Policy kind
- Further enable and improve the UX for managing policies via 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:
- As a user, I can deploy my Configuration/Certificate/OperatorPolicy directly to a cluster from my Git repo via ArgoCD without going through a hub cluster
- As a user, I can centrally visualize the inventory and status of my Configuration/Certificate/OperatorPolicies deployed across my fleet; regardless if they are deployed via the hub Policy kind or in standalone mode
- As a user, I can use ArgoCD as my preferred UX for managing OCM policies, with OOB integrations with ArgoCD (e.g. health checks)
- As a user, I can leverage dependency chaining features in Continuous Delivery tools like ArgoCD sync-waves to conditionally apply a sequence of Policies
Questions to answer
- What are the implications between the ArgoCD push and pull models for this standalone deployment model?
- What should be used on the back-end? Compliance history API, Search, Observability, etc?
- Search: any special handling needed when Search needs to restart and all the data needs to be re-aggregated? What are the impacts to the UX? How does ALC handle this?
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)?
- blocks
-
-
- Closed
-