-
Feature
-
Resolution: Unresolved
-
Major
-
None
-
None
-
False
-
-
False
-
-
Goals
As a DevOps engineer, I need to schedule PipelineRuns on any cluster in our fleet via its API, so that I can gain precise control over where pipelines run, segregate workloads for security and stability, and optimize the overall resource consumption of our CI/CD infrastructure.
Requirements
| Requirements | Notes | IS MVP |
| Clusters in the fleet can either hub and/or spoke | Yes | |
| The Hub has the capability to schedule PipelineRuns on Spokes | Yes | |
| Import manually the Spoke's KubeConfig token in the Hub | Yes | |
| Create a PipelineRun resource on the hub but executed on spoke | Yes |
Out of scope
- WebConsole dedicated UX for import of the Spoke tokens
- Spoke Log collection into the Hub
- Support of non-OpenShift clusters
Dependencies
- Use Kueue APis for job queueing
Assumptions
- The User has two or more OpenShift clusters
- OpenShift Pipelines and Kueue installed in every cluster
Done Checklist
- Requirements are met
- Non-functional properties of the Feature have been validated (such as performance, resource, UX, security or privacy aspects)
- User Journey automation is delivered
- Support and SRE teams are provided with enough skills to support the feature in production environment
- informs
-
SRVKP-8315 Experiment with ACM/OCM
-
- New
-
-
-
- In Progress
-
-
-
- Closed
-
-
SRVKP-8979 Introduce MultiCluster Spec field in Operator
-
- To Do
-
-
-
- To Do
-
-
-
- To Do
-