-
Epic
-
Resolution: Done
-
Normal
-
None
-
managed-vnc-sa-ga
-
-
Green
-
To Do
-
CNV-16970 - Temporary tokens for VNC access
-
0% To Do, 0% In Progress, 100% Done
-
dev-ready, doc-ready, po-ready, qe-ready, ux-ready
-
Goal
A temporary and constrained (time + resource) token to authenticate against the Kubernetes API and gain access to the VNC endpoint of a specific VM can be retrieved from the API
User Stories
- As a 3rd party system, I like to request a new token to access a specific VM, so that I can provide the token to a user
and my user can use the token to access the VNC endpoint.
Non-Requirements
- List of things not included in this epic, to alleviate any doubt raised during the grooming process.
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 | https://polarion.engineering.redhat.com/polarion/#/project/CNV/workitem?id=CNV-9938 |
QE | Automated tests merged | <link or reference to automated tests> |
DOC | Downstream documentation merged | <link to meaningful PR> |