XML

Word

Printable

Epic Name:
routed vnc
Acceptance Criteria:
Hide

Verify that VNC console traffic is not sent on API network to API server and is instead being forwarded to Openshift router and using routed datapath network.

Scale to 20 VNC sessions to verify no performance impact
Show
Verify that VNC console traffic is not sent on API network to API server and is instead being forwarded to Openshift router and using routed datapath network. Scale to 20 VNC sessions to verify no performance impact
Epic Status:
To Do
Hierarchy Progress Bar:

50% To Do, 0% In Progress, 50% Done
Ready-Ready:

dev-ready, po-ready

User Stories

As Cloud Admin, I would like console connectivity (VNC) to be over a regular datapath and not the OpenShift API

Today VNC traffic is encrypted and tunneled on k8s API path. This traffic could congest the API path and slow down critical Admin communication

VNC traffic needs to be forwarded to OpenShift router and routed on datapath

UX work not required for this EPIC

Docs not needed for this EPIC, since this EPIC is for usage of internal network by VNC

DELIVERY OWNER: dkenigsb

QA Engineer: myakove@redhat.com

Done Checklist

DEV - Upstream code and tests merged: <link to meaningful PR or GitHub Issue>
DEV - Upstream roadmap issue: <link to GitHub Issue>
DEV - Upstream documentation merged: <link to meaningful PR or GitHub Issue>
DEV - Downstream build attached to advisory: <link to errata>
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 or GitHub Issue>

is related to

CNV-34314 Scalable VNC

CNV-6281 Console Connectivity (VNC) for guest interaction