XML

Word

Printable

Epic Name:
vm-stable-endpoint
Acceptance Criteria:
Hide

(must-have) Downstream documentation

(must-have) Tier1 test coverage

(must-have) An arbitrary port of a VM exposed through a headless service must be accessible from other VMs and Pods in the given cluster through the VM's FQDN
Show
(must-have) Downstream documentation (must-have) Tier1 test coverage (must-have) An arbitrary port of a VM exposed through a headless service must be accessible from other VMs and Pods in the given cluster through the VM's FQDN
Current Status:
Green
Epic Status:
To Do
Hierarchy Progress Bar:

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

dev-ready, doc-ready, po-ready, qe-ready, ux-ready
Status Summary:

Hide

On track...

Show
On track...
Target Version:

CNV v4.16.0

Goal

Provide stable network endpoint for VM access within the cluster using headless Services.

User Stories

As a developer,
I want to be able to access my VMs on a stable endpoint, no matter the protocol.

<List of things not included in this epic, to alleviate any doubt raised during the grooming process.>

https://kubevirt.io/user-guide/virtual_machines/dns/
This feature is already implemented on the backend and tested in upstream end-to-end tests

Who	What	Reference
DEV	Upstream roadmap issue (or individual upstream PRs)	N/A
DEV	Upstream documentation merged	https://kubevirt.io/user-guide/virtual_machines/dns/
DEV	gap doc updated	N/A
DEV	Upgrade consideration	None
DEV	CEE/PX summary presentation	N/A
QE	Test plans in Polarion	N/A
QE	Automated tests merged	https://gitlab.cee.redhat.com/contra/cnv-qe-automation/-/merge_requests/11506
DOC	Downstream documentation merged	https://github.com/openshift/openshift-docs/pull/76911

is depended on by

CNV-37039 UI: Stable VM network endpoint using headless Services