Skip to content

CNV-80383: Add 6 CNV release notes for 4.22 #112352

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
danielclowers wants to merge 1 commit into
base: enterprise-4.22
Choose a base branch
from
+32 −0
Open

CNV-80383: Add 6 CNV release notes for 4.22 #112352

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
32 changes: 32 additions & 0 deletions virt/release_notes/virt-4-22-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,11 @@ For more information, see xref:../post_installation_configuration/virt-kubevirt-

// Virtualization

Configure PSRP, WINRM, or SSH to discover Windows-detected hosts in OpenShift Virtualization::
You can set a connection method to secure the communication between Windows hosts running on OpenShift Virtualization and the Ansible environment. Configure PowerShell Remote Protocol (PSRP), Windows Remote Management (WINRM), or Secure Shell (SSH) as a connection method in Ansible automation tasks to manage Windows hosts. The Ansible inventory plugin uses the protocol to manage the Windows hosts.
+
link:https://redhat.atlassian.net/browse/CNV-73306[CNV-73306]
Comment thread
danielclowers marked this conversation as resolved.



// Networking
Expand All @@ -56,13 +61,34 @@ With this release, support for IPv6 single-stack clusters is Generally Available
+
link:https://redhat.atlassian.net/browse/CNV-28924[CNV-28924]

Hot swap virtual machine secondary network by switching the NAD without restarting the VM::
Copy link
Copy Markdown

@frenzyfriday frenzyfriday May 27, 2026 •
edited
Loading

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Wondering if this would sound better:

Live update NAD reference for secondary VM networks

  You can now change the Network Attachment Definition (NAD) for a running virtual machine's secondary network interface without rebooting the VM. Edit the networkName field in the VM spec to switch networks
  (for example, to a different VLAN), which triggers a live migration while preserving the guest interface name and MAC address.

But I probably missed the deadline to request the change?

The virtual machine (VM) administrator can hot swap the Virtual Local Area Network (VLAN) uplink guests while the VM is running. You can switch the VLAN ID of a VM by referring the VM network interface to a different Network Attachment Definition (NAD) that has a new VLAN ID. The hot swap capability gives the flexibility to change VLAN networks for a better link or an isolated segment while preserving the guest network identity, without rebooting the VM.
+
link:https://redhat.atlassian.net/browse/CNV-72329[CNV-72329]
Comment thread
danielclowers marked this conversation as resolved.

Define physical networks from an existing node network configuration policy::
Define physical networks based on existing node network configuration policies (NNCPs) in the OpenShift Virtualization user interface. A physical network is a logical grouping of one or more network configurations that represent the NNCP. Cluster administrators can extend a physical network to a set of new nodes, configure a virtual machine that uses the physical network through an OVN-Kubernetes Localnet network, and create new node network configurations for VMs.
+
link:https://redhat.atlassian.net/browse/CNV-72621[CNV-72621]
Comment thread
danielclowers marked this conversation as resolved.


// Storage

New default for PVC naming during VM restore and clone requests::
+
With this update, the `volumeRestorePolicy` default setting has been changed to `PrefixTargetName`. This means that the name of the target virtual machine (VM) is now used as a prefix for new PVC names created with VM restore and clone requests.
+
link:https://redhat.atlassian.net/browse/CNV-77397[CNV-77397]
Comment thread
danielclowers marked this conversation as resolved.



// Web console

Add an internal certificate authority or a self-signed certificate for virtual machine images::
Cluster administrators can create a custom certificate authority (CA) or a self-signed certificate for URL images in a cluster in the Add Volume dialog. As a result, you can secure access to HTTPS sources to be used to create a virtual machine (VM) in a streamlined user workflow, without switching to the command line interface (CLI) for manual patching.
+
link:https://redhat.atlassian.net/browse/CNV-79324[CNV-79324]
Comment thread
danielclowers marked this conversation as resolved.



// Monitoring
Expand Down Expand Up @@ -123,6 +149,12 @@ You can now configure a custom video device type when creating a virtual machine
+
link:https://issues.redhat.com/browse/CNV-71192[CNV-71192]

//CNV-81577
Convert an existing VM to a template from the user interface (Technology Preview)::
Virtual machine (VM) owners can create, filter, and delete a user-generated template. You can create a template from an existing VM in the same project as the running VM or a different project from the OpenShift Virtualization user interface. To make sure that the data is consistent, stop the VM before you create a template. This capability is a Technology Preview feature.
+
link:https://redhat.atlassian.net/browse/CNV-81577[CNV-81577]
Comment thread
danielclowers marked this conversation as resolved.

//[id="virt-4-22-bug-fixes_{context}"]
//== Fixed issues

Expand Down