-
Story
-
Resolution: Done
-
Critical
-
None
-
3
-
False
-
None
-
False
-
SECFLOWOTL-75 - Red Hat Tekton catalog GA
-
-
-
Pipelines Sprint Pioneers 2, Pipelines Sprint Pioneers 3, Pipelines Sprint Pioneers 4, Pipelines Sprint Pioneers 5, Pipelines Sprint Pioneers 6
Story (Required)
In 1.15 __ we will be shipping tektoncd-catalog tasks as a Task in a namespace along with the existing ClusterTask
So we need to provide a migration doc on how to use clusterResolver to use the Task instead of ClusterTask
Consider this https://redhat-internal.slack.com/archives/CSPS1077U/p1713426249501779?thread_ts=1713368411.980159&cid=CSPS1077U while documenting
Background (Required)
<Describes the context or background related to this story>
Out of scope
<Defines what is not included in this story>
Approach (Required)
<Description of the general technical path on how to achieve the goal of the story. Include details like json schema, class definitions>
Dependencies
<Describes what this story depends on. Dependent Stories and EPICs should be linked to the story.>
Acceptance Criteria (Mandatory)
<Describe edge cases to consider when implementing the story and defining tests>
<Provides a required and minimum list of acceptance tests for this story. More is expected as the engineer implements this story>
INVEST Checklist
Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated
Legend
Unknown
Verified
Unsatisfied
Done Checklist
- Code is completed, reviewed, documented and checked in
- Unit and integration test automation have been delivered and running cleanly in continuous integration/staging/canary environment
- Continuous Delivery pipeline(s) is able to proceed with new code included
- Customer facing documentation, API docs etc. are produced/updated, reviewed and published
- Acceptance criteria are met
- is documented by
-
RHDEVDOCS-6074 Change from ClusterTasks to cluster resolver
-
- Closed
-