-
Epic
-
Resolution: Done
-
Normal
-
None
-
custom-golden-images-namespace
-
False
-
-
False
-
- The cluster admin is able to deploy the common golden images into a custom namespace, to hide them in the cluster users UI
-
Green
-
To Do
-
CNV-30153 - Golden Images
-
-
0% To Do, 0% In Progress, 100% Done
-
dev-ready, doc-ready, po-ready, qe-ready, ux-ready
-
-
---
-
---
Goal
Because PVCs objects will be read by the UI to identify "golden images", the namespace of the default PVCs must be configurable.
This provides compatibility with the configurable namespaces for templates.
The use-case is to give an admin the power to deploy the golden images in a non-default namespace, to use them in a pipeline, and use the pipeline output as golden images.
User Stories
- As an admin I want to deploy the default boot sources into a namespace not accessible by the users, so that I can decide which images will be accessible by the user.
Non-Requirements
- This epic does not cover to have the namespace of the datasources configurable.
Notes
- Any additional details or decisions made/needed
Done Checklist
| Who | What | Reference |
|---|---|---|
| DEV | Upstream roadmap issue (or individual upstream PRs) | <link to GitHub Issue> |
| DEV | Upstream documentation merged | <link to meaningful PR> |
| DEV | gap doc updated | <name sheet and cell> |
| DEV | Upgrade consideration | <link to upgrade-related test or design doc> |
| DEV | CEE/PX summary presentation | label epic with cee-training and add a <link to your support-facing preso> |
| QE | Test plans in Polarion | <link or reference to Polarion> |
| QE | Automated tests merged | <link or reference to automated tests> |
| DOC | Downstream documentation merged | <link to meaningful PR> |
