-
Epic
-
Resolution: Done
-
Major
-
None
-
None
-
Multiarch Tuning Operator 1.0 Productization (Release Epic)
-
Quality / Stability / Reliability
-
0% To Do, 0% In Progress, 100% Done
-
False
-
-
False
-
None
-
None
-
None
Do not update this Epic/Tasks directly. The template should be cloned and applied to the onboarding of your operator
Hello, welcome to the self-guided Onboarding template for productizing OpenShift Layered Services.
You are here because you are looking to productize/release a Major (X release) or Minor (Y release) update of Day2 operator for OpenShift utilizing CPaaS pipeline.
Guidelines for using this template:
1. Clone the template by selecting 'More' -> 'Clone Operators Productization Template' from the drop-down.
2. Update the Summary, Epic Name, and Description with your operator information.
3.a. You may move the cloned Epic and the child tasks to your own Jira Project by using Bulk Editing
- Search for the cloned Epic and its child tasks by typing in Search Bar: id in (your cloned Epic ID) OR id in childIssuesOf(your cloned Epic ID) order by Rank. Eg. id in (PLMPGM-3872) OR id in childIssuesOf(PLMPGM-3872) order by Rank ASC
- Go to Tools on the top right corner
- Bulk Change All 12 Tasks
- Move Tasks
- Select your JIRA Project
- Associate all tasks to the Epic Link
- Please note if you are moving the cloned Epics and child tasks to a Public Jira Project, you will need to keep the cloned Epic and child tasks as private (eg. Security Level field needs to be set as "Red Hat Employee"). The Jira automation should automatically apply "Red Hat Employee" for Security Level field to the cloned Epic and child tasks but please double check to make sure they are set properly.
3.b. Set the Target End Date as your estimated GA Release date. Tips: if you are unsure what to set for the Target End Date for now, it typically takes 60 days from the Target Start Date to release major/minor update for operators. You may add 60 days from the Target Start Date to get the initial GA release date and set that date as your End Date in the Epic
4. Read and follow the instructions in each task
5. Assign Jira tasks to the appropriate team member and keep a record in Jira of what's been done before closing out. If a decision was made to not complete a task please comment on the reasoning and risk assessment carried out.
6. Please ensure there is label "OperatorProductization" on the Epic
7. If you have any questions, please reach out to your Program Manager or Ramona Sidharta for assistance
Resources:
- depends on
-
MULTIARCH-4264 [MultiArch-Tuning] Disconnected scenarios
-
- Closed
-
-
MULTIARCH-4257 [MultiArch-Tuning] Performance testing/tuning
-
- Closed
-
-
MULTIARCH-4783 [MultiArch-Tuning] Ordered uninstallation
-
- Closed
-
-
MULTIARCH-4781 [MultiArch-Tuning] Inspection caching
-
- Closed
-
- is related to
-
MULTIARCH-4985 Run DAST on MTO webhook and pod placement controller
-
- Closed
-