Skip to content

Commit 78b460d

Browse files
danielclowersdanielclowers
committed
CNV#57755: RN 4.20 shell file
1 parent bb9088a commit 78b460d

File tree

2 files changed

+37
-125
lines changed

2 files changed

+37
-125
lines changed

‎_topic_maps/_topic_map.yml

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -4649,7 +4649,7 @@ Topics:
46494649
Distros: openshift-enterprise
46504650
Topics:
46514651
- Name: OpenShift Virtualization release notes
4652-
File: virt-4-19-release-notes
4652+
File: virt-4-20-release-notes
46534653
- Name: Getting started
46544654
Dir: getting_started
46554655
Topics:

‎virt/release_notes/virt-4-19-release-notes.adoc renamed to ‎virt/release_notes/virt-4-20-release-notes.adoc

Lines changed: 36 additions & 124 deletions
Original file line numberDiff line numberDiff line change
@@ -1,8 +1,8 @@
11
:_mod-docs-content-type: ASSEMBLY
2-
[id="virt-4-19-release-notes"]
2+
[id="virt-4-20-release-notes"]
33
= {VirtProductName} release notes
44
include::_attributes/common-attributes.adoc[]
5-
:context: virt-4-19-release-notes
5+
:context: virt-4-20-release-notes
66

77
toc::[]
88

@@ -52,132 +52,44 @@ The SVVP certification applies to:
5252
Quick start tours are available for several {VirtProductName} features. To view the tours, click the *Help* icon *?* in the menu bar on the header of the {product-title} web console and then select *Quick Starts*. You can filter the available tours by entering the keyword `virtualization` in the *Filter* field.
5353

5454

55-
[id="virt-4-19-new_{context}"]
55+
[id="virt-4-20-new_{context}"]
5656
== New and changed features
5757

5858
This release adds new features and enhancements related to the following components and concepts:
5959

60-
//[id="virt-4-19-installation-update_{context}"]
61-
//=== Installation and update
62-
//[id="virt-4-19-installation-update"]
63-
//=== Installation and update
6460

65-
[id="virt-4-19-infrastructure_{context}"]
66-
=== Infrastructure
67-
//[id="virt-4-19-infrastructure"]
68-
//=== Infrastructure
61+
[id="virt-4-20-installation-update_{context}"]
62+
=== Installation and update
6963

70-
//CNV-49593
71-
* You can now prevent the inadvertent deletion of a virtual machine (VM) by xref:../../virt/managing_vms/virt-enabling-disabling-vm-delete-protection.adoc#virt-enabling-disabling-vm-delete-protection[enabling delete protection for the VM]. You can also disable delete protection that has been set for a VM.
72-
+
73-
As a cluster administrator, you can prevent users from enabling VM delete protection xref:../../virt/managing_vms/virt-enabling-disabling-vm-delete-protection.adoc#virt-removing-vm-delete-protection_virt-enabling-disabling-vm-delete-protection[by removing the option at the cluster level].
64+
[id="virt-4-20-infrastructure_{context}"]
65+
=== Infrastructure
7466

75-
[id="virt-4-19-virtualization_{context}"]
67+
[id="virt-4-20-virtualization_{context}"]
7668
=== Virtualization
7769

78-
//CNV-54747
79-
* You can now choose to expand virtual machines (VMs) using instance types and preferences. For more information, see link:https://access.redhat.com/solutions/7107803[Using InstancetypeReferencePolicy to expand VirtualMachines] in the Red Hat Customer Portal.
80-
//CNV-58007
81-
* {op-system-base-full} 10 is added as a certified guest operating system. For a complete list of supported guest operating systems, see link:https://access.redhat.com/articles/4234591[Certified Guest Operating Systems in OpenShift Virtualization].
82-
83-
//CNV-54610: Release note: Mass machine type change procedure
84-
* You can now xref:../../virt/managing_vms/virt-edit-vms.adoc#virt-updating-multiple-vms_virt-edit-vms[update the machine type of multiple virtual machines (VMs) at the same time] from the {oc-first}.
85-
86-
[id="virt-4-19-networking_{context}"]
70+
[id="virt-4-20-networking_{context}"]
8771
=== Networking
8872

89-
//CNV-30151 NNCP to enable LLDP
90-
* You can now xref:../../networking/k8s_nmstate/k8s-nmstate-updating-node-network-config.adoc#virt-example-enabling-lldp-policy_k8s-nmstate-updating-node-network-config[configure a `NodeNetworkConfigurationPolicy` manifest] to enable the Link Layer Discovery Protocol (LLDP) listener for all ethernet ports in your {product-title} cluster.
91-
//CNV-55191 Host network configuration visualization
92-
* You can now create a new Node Network Configuration Policy (NNCP) in the topology view of the cluster and see its graphical representation in real time. Clicking *Create* on the *Node network configuration* page opens a form for configuring the elements of the new NNCP, and the NNCP is also displayed as a diagram.
93-
94-
//CNV-52856 UDN localnet
95-
* You can now use the OVN-Kubernetes localnet network topology to connect a VM to a xref:../../virt/vm_networking/virt-connecting-vm-to-secondary-udn.adoc#virt-connecting-vm-to-secondary-udn[secondary user-defined network].
96-
97-
98-
[id="virt-4-19-storage_{context}"]
73+
[id="virt-4-20-storage_{context}"]
9974
=== Storage
10075

101-
//CNV-55497 Doc: PVC source support for DataImportCron
102-
* You can now use a PVC as the source of a custom `DataImportCron` in the `dataImportCronTemplates` section of the `HyperConverged` custom resource (CR). See xref:../../virt/storage/virt-automatic-bootsource-updates.adoc#virt-automatic-bootsource-updates[Managing automatic boot source updates] for more information.
103-
104-
//CNV-58547 UI - Bulk Storage Class Migration within a single cluster
105-
* By using the {product-title} web console, you can now xref:../../virt/managing_vms/virt-migrating-vms-in-single-cluster-to-different-storage-class.adoc#virt-migrating-bulk-vms-different-storage-class-web_virt-migrating-vms-in-single-cluster-to-different-storage-class[migrate VMs in bulk from one storage class to another storage class].
106-
107-
108-
[id="virt-4-19-web_{context}"]
76+
[id="virt-4-20-web_{context}"]
10977
=== Web console
11078

111-
// CNV-52871 - Doc: Multi IOthread with fast storage
112-
* You can now xref:../../virt/managing_vms/virt-edit-vms.adoc#virt-configure-multiple-iothreads_virt-edit-vms[configure multiple IOThreads for virtual machines that use fast storage], such as SSD (solid-state drive) or NVMe (non-volatile memory express). This improves I/O performance by enabling multiple threads for disk access.
113-
114-
// CNV-56843:
115-
* On the *VirtualMachines* page, you can now xref:../../virt/support/virt-support-overview.adoc#virt-web-console_virt-support-overview[see the summary of CPU, memory, and storage usage by your VMs]. To restrict this summary to the VMs in a specific project, select the project name in the tree view.
116-
117-
// CNV-55958:
118-
* On the *VirtualMachines* page, you can now xref:../../virt/managing_vms/virt-list-vms.adoc#virt-listing-vms-web_virt-list-vms[navigate between your VMs by using the tree view].
119-
120-
//CNV-56275
121-
* An attempt to xref:../../virt/managing_vms/virt-controlling-vm-states.adoc#virt-controlling-vm-states[stop, restart, or pause a VM or multiple VMs] now displays a confirmation dialog.
122-
123-
//CNV-55965
124-
* You can now access xref:../../virt/managing_vms/virt-controlling-vm-states.adoc#virt-controlling-vm-states[the commands of the *Options* menu] {kebab} from the tree view by right-clicking the VM. If you right-click a project and select a command, the action is applied to all VMs in the project.
125-
//CNV-59097
126-
* You can now perform bulk actions on multiple virtual machines (VMs), including adding or removing labels, viewing the number of VMs selected for deletion, and moving VMs to a folder within the same namespace.
127-
128-
// CNV-56003:
129-
* On the *VirtualMachines* page, you can now xref:../../virt/managing_vms/virt-list-vms.adoc#virt-organize-vms-web_virt-list-vms[use the tree view to organize VMs in folders] and drag and drop VMs to these folders.
130-
131-
// CNV-56266: Advanced search for VMs
132-
* You can now xref:../../virt/managing_vms/virt-manage-vmis.adoc#virt-searching-vmis-web_virt-manage-vmis[search for virtual machines] by fields such as name, project, description, labels, date created, vCPU, and memory. You can also save frequently used search queries.
133-
134-
135-
[id="virt-4-19-monitoring_{context}"]
79+
[id="virt-4-20-monitoring_{context}"]
13680
=== Monitoring
13781

138-
//CNV-59720
139-
* The following xref:../../virt/monitoring/virt-runbooks.adoc#virt-runbooks[alerts for the {CNVOperatorDisplayName}] are now included in the {product-title} runbooks:
140-
** `HAControlPlaneDown`
141-
** `HighCPUWorkload`
142-
** `NodeNetworkInterfaceDown`
82+
[id="virt-4-20-documentation_{context}"]
83+
=== Documentation improvements
14384

144-
//CNV-50346
145-
* New metrics are now available and improve the observability of virtual machines (VMs) and virtual machine instances (VMIs). You can use these metrics to monitor the following VM lifecycle events, resource usage, and migration details:
146-
+
147-
--
148-
** Migration metrics
149-
** vNIC networking information metrics
150-
** Allocated storage size metrics for running and stopped VMs
151-
--
152-
+
153-
In addition, the following VM and VMI metadata metrics are now available:
154-
+
155-
--
156-
** The `pod_name` label in `kubevirt_vmi_info`
157-
** UID in VM and VMI metrics
158-
** The VM creation date
159-
--
160-
+
161-
For a complete list of virtualization metrics, see link:https://github.com/kubevirt/monitoring/blob/main/docs/metrics.md[KubeVirt components metrics].
162-
163-
//[id="virt-4-19-documentation_{context}"]
164-
//=== Documentation improvements
165-
166-
167-
[id="virt-4-19-notable-technical-changes_{context}"]
85+
[id="virt-4-20-notable-technical-changes_{context}"]
16886
=== Notable technical changes
16987

170-
// CNV-48243: RN - Support declarative VirtualMachine management with instance types
171-
* VirtualMachines that use instance types and preferences no longer have their specification mutated at runtime to include derived metadata, such as `revisionName`. This metadata is now stored in the `status` field to preserve the declarative VM specification and ensure compatibility.
172-
173-
//CNV-57108
174-
* In {VirtProductName} 4.19, the default permissions for live migration have changed to improve cluster security. Users must now be explicitly granted the `kubevirt.io:migrate` xref:../../virt/about_virt/virt-security-policies.adoc#default-cluster-roles-for-virt_virt-security-policies[cluster role] to create, delete, or update live migration requests. Previously, namespace administrators had these permissions by default. For more information, see xref:../../virt/live_migration/virt-about-live-migration.adoc#virt-about-live-migration-permissions_virt-about-live-migration[About live migration permissions].
17588

176-
[id="virt-4-19-deprecated-removed_{context}"]
89+
[id="virt-4-20-deprecated-removed_{context}"]
17790
== Deprecated and removed features
178-
//NOTE: Comment out deprecated and removed features (and their IDs) if not used in a release
17991

180-
[id="virt-4-19-deprecated_{context}"]
92+
[id="virt-4-20-deprecated_{context}"]
18193
=== Deprecated features
18294
// NOTE: When uncommenting deprecated features list, change the Removed features header level below to ===
18395

@@ -195,12 +107,13 @@ Deprecated features are included in the current release and supported. However,
195107
+
196108
If used in the `spec.featureGates` location, the old fields are ignored.
197109

198-
//[id="virt-4-19-removed_{context}"]
199-
//=== Removed features
110+
[id="virt-4-20-removed_{context}"]
111+
=== Removed features
200112

201-
//Removed features are no longer supported in {VirtProductName}.
113+
Removed features are no longer supported in {VirtProductName}.
202114

203-
[id="virt-4-19-technology-preview_{context}"]
115+
116+
[id="virt-4-20-technology-preview_{context}"]
204117
== Technology Preview features
205118

206119
Some features in this release are currently in Technology Preview. These experimental features are not intended for production use. Note the following scope of support on the Red Hat Customer Portal for these features:
@@ -219,34 +132,33 @@ link:https://access.redhat.com/support/offerings/techpreview[Technology Preview
219132
//CNV-62829
220133
* You can now deploy {VirtProductName} on IPv6 single-stack clusters. Support for IPv6 single-stack is limited to the OVN-Kubernetes localnet and Linux bridge Container Network Interface (CNI) plugins.
221134

222-
//[id="virt-4-19-bug-fixes_{context}"]
223-
//== Bug fixes
135+
[id="virt-4-20-bug-fixes_{context}"]
136+
== Bug fixes
224137

225138

226-
[id="virt-4-19-known-issues_{context}"]
139+
[id="virt-4-20-known-issues_{context}"]
227140
== Known issues
228141

229-
//[discrete]
230-
//[id="virt-4-19-ki-monitoring_{context}"]
231-
//=== Monitoring
142+
[discrete]
143+
[id="virt-4-20-ki-monitoring_{context}"]
144+
=== Monitoring
232145

233146
[discrete]
234-
[id="virt-4-19-ki-networking_{context}"]
147+
[id="virt-4-20-ki-networking_{context}"]
235148
=== Networking
236149
//CNV-38746
237150
* When you update from {product-title} 4.12 to a newer minor version, VMs that use the `cnv-bridge` Container Network Interface (CNI) fail to live migrate. (link:https://access.redhat.com/solutions/7069807[])
238151
** As a workaround, change the `spec.config.type` field in your `NetworkAttachmentDefinition` manifest from `cnv-bridge` to `bridge` before performing the update.
239152

240153

241-
242154
[discrete]
243-
[id="virt-4-19-ki-nodes_{context}"]
155+
[id="virt-4-20-ki-nodes_{context}"]
244156
==== Nodes
245157
//CNV-38543 - 4.16 Still an issue
246158
* Uninstalling {VirtProductName} does not remove the `feature.node.kubevirt.io` node labels created by {VirtProductName}. You must remove the labels manually. (link:https://issues.redhat.com/browse/CNV-38543[*CNV-38543*])
247159

248160
[discrete]
249-
[id="virt-4-19-ki-storage_{context}"]
161+
[id="virt-4-20-ki-storage_{context}"]
250162
==== Storage
251163

252164
//CNV-61279: 4.19 - Storage Migrate VM with MTC
@@ -262,7 +174,7 @@ include::snippets/technology-preview.adoc[]
262174
--
263175

264176
[discrete]
265-
[id="virt-4-19-ki-virtualization_{context}"]
177+
[id="virt-4-20-ki-virtualization_{context}"]
266178
=== Virtualization
267179

268180
//CNV-48348
@@ -275,12 +187,12 @@ include::snippets/technology-preview.adoc[]
275187
//CNV-36448
276188
* When adding a virtual Trusted Platform Module (vTPM) device to a Windows VM, the BitLocker Drive Encryption system check passes even if the vTPM device is not persistent. This is because a vTPM device that is not persistent stores and recovers encryption keys using ephemeral storage for the lifetime of the virt-launcher pod. When the VM migrates or is shut down and restarts, the vTPM data is lost. (link:https://issues.redhat.com/browse/CNV-36448[CNV-36448])
277189

278-
//[discrete]
279-
//[id="virt-4-19-ki-webconsole_{context}"]
280-
//=== Web console
190+
[discrete]
191+
[id="virt-4-20-ki-webconsole_{context}"]
192+
=== Web console
281193

282194
[discrete]
283-
[id="virt-4-19-ki-ibm-z_{context}"]
195+
[id="virt-4-20-ki-ibm-z_{context}"]
284196
=== {ibm-z-title} and {ibm-linuxone-title}
285197

286198
ifdef::openshift-enterprise[]

0 commit comments

Comments
 (0)