-
Epic
-
Resolution: Done
-
Minor
-
None
-
None
-
None
-
vnc-console
-
- VNC access not going through the API server
- Authenticated access
- Encrypted connection
- Horizontally Scalable
-
50% To Do, 0% In Progress, 50% Done
-
dev-ready, po-ready, qe-ready, ux-ready
User Stories
I am sitting outside the KNI cluster, and would like to connect securely to my VM console(s)
User stories 1: Legacy clients
- As a VM owner I would like to use GUI/virtctl to obtain a token to my VM as well as IP:port combination. I would like to later run s_client IP port (or an equivalent, such as socat), type in my token, and have access to the console of my VM.
- As a VM owner I would like to use GUI/virtctl to obtain a .vv file with token to my VM as well as IP:port combination. I would like to later run virt-viewer foobar.vv and connect to my VM
As an owner of a Windows VM which is connected via the Pod network, I would like to log into it, configure RDP server on it and set its password. I would like to use GUI/virtctl to obtain an IP:port combination. I would like to later run xfreerpd IP:port, pass my password, and connect to my VM.
User Stories 2: Thin Client
As a VM owner, I would like to be able to connect to my VM via VNC while using only my browser.
User Stories 3: virtctl vm name console
As a VM owner, I would like to `oc login` to my cluster, and then use a single command line to access the console of my VM.
REFERENCES
Initial design diagrams: https://docs.google.com/document/d/1ga4jHn_o63kYd0IURWyla7wSBZsXcCaNFzBY6BrimYo
DELIVERY OWNER: dkenigsb
QA Engineer: myakove@redhat.com
Done Checklist
- DEV - Upstream code and tests merged:
- DEV - Upstream roadmap issue: <link to GitHub Issue>
- DEV - Upstream documentation merged:
- DEV - Downstream build attached to advisory:
- QE - Test plans in Polarion:
- QE - Automated tests merged: <link or reference to automated tests>
- DOC - Downstream documentation merged: Not done
