XML

Word

Printable

Epic Name:
no-running-field
Story Points:
77
Acceptance Criteria:
Hide

DRAFT CRITERIA

Remove usage of .running from all examples and documentation

Emit a deprecation warning if this field is used via the API
Show
DRAFT CRITERIA Remove usage of .running from all examples and documentation Emit a deprecation warning if this field is used via the API
Current Status:
Green
Epic Status:
To Do
Feature Link:
CNV-38613 - 2024 Code Quality
Parent Link:
CNV-386132024 Code Quality
Hierarchy Progress Bar:

0% To Do, 4% In Progress, 96% Done
Status Summary:

Hide

2025-02-03:
only docs remain...

Show
2025-02-03: only docs remain...

Goal

VM owners should use RunStrategy rather than Running field. The Running field should have been deprecated when RunStrategy was introduced. See https://github.com/kubevirt/kubevirt/issues/11993

User Stories

As a VM owner, I want to my VM to use only the recommended modern field, whenever I run my VMs (GUI, templates, doc, examples)

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

clones

CNV-4600 CNV Epic Template

1.	upstream roadmap issue	Closed	Unassigned
2.	upstream design	New	Unassigned
3.	upstream documentation	Closed	Unassigned
4.	upgrade consideration	New	Unassigned
5.	CEE/PX summary presentation	Closed	Unassigned
6.	test plans in polarion	Closed	Unassigned
7.	automated tests	Closed	Unassigned
8.	downstream documentation merged	Stakeholder Acceptance	Sasha Beskin