Skip to content
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

[enterprise-4.17] CNV#40185: RN shell file 4.17 #79779

Merged
merged 1 commit into from
Aug 1, 2024
Merged

[enterprise-4.17] CNV#40185: RN shell file 4.17 #79779

Show file tree
Hide file tree
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
2 changes: 1 addition & 1 deletion _topic_maps/_topic_map.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -4147,7 +4147,7 @@ Topics:
Distros: openshift-enterprise
Topics:
- Name: OpenShift Virtualization release notes
File: virt-4-16-release-notes
File: virt-4-17-release-notes
- Name: Getting started
Dir: getting_started
Topics:
Expand Down
90 changes: 31 additions & 59 deletions ...elease_notes/virt-4-16-release-notes.adoc → ...elease_notes/virt-4-17-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,8 +1,8 @@
:_mod-docs-content-type: ASSEMBLY
[id="virt-4-16-release-notes"]
[id="virt-4-17-release-notes"]
= {VirtProductName} release notes
include::_attributes/common-attributes.adoc[]
:context: virt-4-16-release-notes
:context: virt-4-17-release-notes

toc::[]

Expand Down Expand Up @@ -52,74 +52,40 @@ The SVVP certification applies to:
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.


[id="virt-4-16-new"]
[id="virt-4-17-new"]
== New and changed features

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

[id="virt-4-16-installation-update"]
[id="virt-4-17-installation-update"]
=== Installation and update

//CNV-38590
* After upgrading to {VirtProductName} {product-version}, data volumes that were previously removed through garbage collection might be recreated. This behavior is expected and the recreated data volumes should be ignored now that data volume garbage collection is disabled.

[id="virt-4-16-infrastructure"]
[id="virt-4-17-infrastructure"]
=== Infrastructure

[id="virt-4-16-virtualization"]
[id="virt-4-17-virtualization"]
=== Virtualization

//CNV-29170 Real-time cluster configuration (Uncomment the note below when feature goes out with a 4.16.z release)
//* You can xref:../../virt/virtual_machines/advanced_vm_management/virt-configuring-cluster-realtime-workloads.adoc#virt-configuring-cluster-realtime-workloads[configure an {product-title} cluster] to run real-time virtual machine (VM) workloads that require low and predictable latency.

//CNV-29192 Running real-time checkup (Uncomment the note below when feature goes out with a 4.16.z release)
//* You can now run a predefined xref:../../virt/monitoring/virt-running-cluster-checkups.adoc#virt-running-real-time-checkup_virt-running-cluster-checkups[checkup] to verify that your {product-title} cluster is configured to run virtualized real-time workloads.

//CNV-33366 Release note: NEW - Adopt UEFI in all Windows versions
* Windows 10 VMs now boot using UEFI with TPM.

//CNV-29984: RN - Document auto memory and cpu resource limits
* Enabling the `AutoResourceLimits` feature gate automatically manages CPU and memory limits of a VM.

[id="virt-4-16-networking"]
[id="virt-4-17-networking"]
=== Networking

//CNV-37037 headless services support
* You can now xref:../../virt/vm_networking/virt-accessing-vm-internal-fqdn.adoc#virt-accessing-vm-internal-fqdn[access a VM] that is connected to the default internal pod network on a stable fully qualified domain name (FQDN) by using headless services.

[id="virt-4-16-storage"]
[id="virt-4-17-storage"]
=== Storage

[id="virt-4-16-web"]
[id="virt-4-17-web"]
=== Web console

//CNV-34687 Release note: Generally available (GA) CPU Hotplug
* Hot plugging virtual machines is now generally available. If a virtual machine cannot be hot plugged, the condition `RestartRequired` is applied to the VM. You can view this condition in the *Diagnostics* tab of the web console.

[id="virt-4-16-monitoring"]
[id="virt-4-17-monitoring"]
=== Monitoring

//CNV-41655 Release note: NEW Downward Metrics 4.16
* As an administrator, you can now xref:../../virt/monitoring/virt-exposing-downward-metrics.adoc#virt-exposing-downward-metrics[expose a limited set of host and virtual machine (VM) metrics to a guest VM through a virtio-serial port] for {VirtProductName} by enabling a `downwardMetrics` feature gate and configuring a `downwardMetrics` device. Users retrieve the metrics by using the `vm-dump-metrics` tool or from the command line.
+
On {op-system-base-full} 9, xref:../../virt/monitoring/virt-exposing-downward-metrics.adoc#virt-viewing-downward-metrics-cli_virt-exposing-downward-metrics[use the command line] to view downward metrics. The `vm-dump-metrics` tool is not supported on the {op-system-base-full} 9 platform.

[id="virt-4-16-notable-technical-changes"]
[id="virt-4-17-notable-technical-changes"]
=== Notable technical changes

//CNV-43342: RN: VMs require 1GiB memory
* VMs require a minimum of 1 GiB of allocated memory to enable memory hotplug. If a VM has less than 1 GiB of allocated memory, then memory hotplug is disabled.

//CNV-34681: runbooks moved to openshift/runbooks repo
* Runbooks for {VirtProductName} alerts are now maintained only in the https://github.com/openshift/runbooks/tree/master/alerts/openshift-virtualization-operator[`openshift/runbooks` git repository] and have been removed from the documentation.
+
In a future release, alerts will link directly to the runbook source files. However, in {VirtProductName} {VirtVersion} and earlier, the alerts link to the documentation. In these versions of the documentation, xref:../../virt/monitoring/virt-runbooks.adoc#virt-runbooks[links to the runbook source files] are now available in place of the removed runbooks.

[id="virt-4-16-deprecated-removed"]
[id="virt-4-17-deprecated-removed"]
== Deprecated and removed features
//NOTE: Comment out deprecated and removed features (and their IDs) if not used in a release

[id="virt-4-16-deprecated"]
[id="virt-4-17-deprecated"]
=== Deprecated features
// NOTE: When uncommenting deprecated features list, change the Removed features header level below to ===

Expand All @@ -137,12 +103,12 @@ Deprecated features are included in the current release and supported. However,
//CNV-34681: Deprecated alerts
* The alerts `KubeVirtComponentExceedsRequestedMemory` and `KubeVirtComponentExceedsRequestedCPU` are deprecated. You can safely xref:../../observability/monitoring/managing-alerts.adoc#silencing-alerts_managing-alerts[silence] them.

[id="virt-4-16-removed"]
[id="virt-4-17-removed"]
=== Removed features

Removed features are not supported in the current release.

[id="virt-4-16-technology-preview"]
[id="virt-4-16-technology-preview_{context}"]
== Technology Preview features

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:
Expand All @@ -158,36 +124,39 @@ link:https://access.redhat.com/support/offerings/techpreview[Technology Preview
//CNV-33125: Add CPU limits to the UI
* Cluster admins can now enable CPU resource limits on a namespace in the {product-title} web console under *Overview* -> *Settings* -> *Preview features*.

//CNV-22314: Safe memory overcommitment using `wasp-agent`
* Cluster admins can now use the `wasp-agent` tool to xref:../../virt/virtual_machines/virt-configuring-higher-vm-workload-density.adoc#virt-configuring-higher-vm-workload-density[configure a higher VM workload density] in their clusters by overcommitting the amount of memory, in RAM, and assigning swap resources to VM workloads.

//CNV-31997: PREVIEW - compatibility with ODF Regional DR
* {VirtProductName} now supports compatibility with OpenShift Data Foundation (ODF) Regional Disaster Recovery.
* {VirtProductName} now supports compatibility with {rh-storage-first} (ODF) Regional Disaster Recovery.

[id="virt-4-16-bug-fixes"]
[id="virt-4-17-bug-fixes"]
== Bug fixes

[id="virt-4-16-known-issues"]
[id="virt-4-17-known-issues"]
== Known issues

[discrete]
[id="virt-4-16-ki-monitoring"]
[id="virt-4-17-ki-monitoring"]
==== Monitoring
//CNV-33834: 4.16 - Antonio Cardace said this is still an issue
* The Pod Disruption Budget (PDB) prevents pod disruptions for migratable virtual machine images. If the PDB detects pod disruption, then `openshift-monitoring` sends a `PodDisruptionBudgetAtLimit` alert every 60 minutes for virtual machine images that use the `LiveMigrate` eviction strategy. (link:https://issues.redhat.com/browse/CNV-33834[*CNV-33834*])
** As a workaround, xref:../../observability/monitoring/managing-alerts.adoc#silencing-alerts_managing-alerts[silence alerts].

[discrete]
[id="virt-4-16-ki-networking"]
[id="virt-4-17-ki-networking"]
==== Networking


[discrete]
[id="virt-4-16-ki-nodes"]
[id="virt-4-17-ki-nodes"]
==== Nodes
//CNV-38543 - 4.16 Still an issue
* 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*])


[discrete]
[id="virt-4-16-ki-storage"]
[id="virt-4-17-ki-storage"]
==== Storage
//CNV-32695: 4.16 - Keep per Jenia Peimer
* If you use Portworx as your storage solution on AWS and create a VM disk image, the created image might be smaller than expected due to the filesystem overhead being accounted for twice. (link:https://issues.redhat.com/browse/CNV-40217[*CNV-40217*])
Expand All @@ -204,7 +173,7 @@ link:https://access.redhat.com/support/offerings/techpreview[Technology Preview


[discrete]
[id="virt-4-16-ki-virtualization"]
[id="virt-4-17-ki-virtualization"]
==== Virtualization

//CNV-43195: 4.16 - VM migration fails with virError
Expand All @@ -227,8 +196,11 @@ Legacy OpenSSL clients that do not support EMS or TLS 1.3 now cannot connect to


[discrete]
[id="virt-4-16-ki-webconsole"]
[id="virt-4-16-ki-webconsole_{context}"]
==== Web console
//CNV-38293: 4.16 - Ronen Sde-Or said this was still an issue
* When you first deploy an {product-title} cluster, creating VMs from templates or instance types by using the web console, fails if you do not have `cluster-admin` permissions.
** As a workaround, the cluster administrator must first xref:../../nodes/pods/nodes-pods-configmaps.adoc#nodes-pods-configmap-create-from-console_configmaps[create a config map] to enable other users to use templates and instance types to create VMs. (link: https://issues.redhat.com/browse/CNV-38284[*CNV-38284*])
** As a workaround, the cluster administrator must first xref:../../nodes/pods/nodes-pods-configmaps.adoc#nodes-pods-configmap-create-from-console_configmaps[create a config map] to enable other users to use templates and instance types to create VMs. (link:https://issues.redhat.com/browse/CNV-38284[*CNV-38284*])

//CNV-38594: 4.16 known issue
* When you create a persistent volume claim (PVC) by selecting *With Data upload form* from the *Create PersistentVolumeClaim* list in the web console, uploading data to the PVC by using the *Upload Data* field fails. (link:https://issues.redhat.com/browse/CNV-37607[*CNV-37607*])