Skip to content

OSDOCS-16185: Release note for new OCI infra types #100282

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
wants to merge 1 commit into
base: enterprise-4.20
Choose a base branch
from
Open

OSDOCS-16185: Release note for new OCI infra types #100282

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
37 changes: 28 additions & 9 deletions release_notes/ocp-4-20-release-notes.adoc
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -74,7 +74,7 @@ The default namespace for the {lvms} Operator is now `openshift-lvm-storage`. Yo
[id="ocp-release-edge-computing-default-clusterinstance_{context}"]
==== SiteConfig CR to ClusterInstance CR migration tool

{product-title} {product-version} introduces the `siteconfig-converter` tool to help migrate managed clusters from using a `SiteConfig` custom resource (CR) to a `ClusterInstance` CR. Using a `SiteConfig` CR to define a managed cluster is deprecated and will be removed in a future release. The `ClusterInstance` CR provides a more unified and generic approach to defining clusters and is the preferred method for managing cluster deployments in the {ztp} workflow.
{product-title} {product-version} introduces the `siteconfig-converter` tool to help migrate managed clusters from using a `SiteConfig` custom resource (CR) to a `ClusterInstance` CR. Using a `SiteConfig` CR to define a managed cluster is deprecated and will be removed in a future release. The `ClusterInstance` CR provides a more unified and generic approach to defining clusters and is the preferred method for managing cluster deployments in the {ztp} workflow.

Using the `siteconfig-converter` tool, you can convert `SiteConfig` CRs to `ClusterInstance` CRs and then incrementally migrate one or more clusters at a time. Existing and new pipelines run in parallel, so you can migrate clusters in a controlled, phased manner and without downtime.

Expand Down Expand Up @@ -478,11 +478,30 @@ With this release, you can install a cluster on {azure-short} using Intel-based

For more information, see xref:../installing/installing_azure/ipi/installing-azure-customizations.adoc#installation-azure-confidential-vms_installing-azure-customizations[Enabling confidential VMs].

[id="ocp-release-notes-installation-oci-offerings_{context}"]
==== Additional Oracle Distributed Cloud and Oracle Edge Cloud infrastructure offerings available as Technology Preview

With this release, you can install a Technology Preview cluster on new Oracle infrastructure offerings.

The following new Oracle Distributed Cloud infrastructure types are now available:

* US Government Cloud
* UK Government Cloud
* EU Sovereign Cloud
* Isolated Region
* Oracle Alloy

The following new Oracle Edge Cloud infrastructure type is now available:

* Roving Edge

For more information, see

[id="ocp-release-notes-machine-config-operator_{context}"]
=== Machine Config Operator

[id="ocp-release-notes-machine-config-operator-boot_{context}"]
==== Updated boot images for vSphere now supported (Technology Preview)
==== Updated boot images for vSphere now supported (Technology Preview)

Updated boot images is now supported as a Technology Preview feature for {vmw-first} clusters. This feature allows you configure your cluster to update the node boot image whenever you update your cluster. By default, the boot image in your cluster is not updated along with your cluster. For more information, see xref:../machine_configuration/mco-update-boot-images.adoc#mco-update-boot-images[Updated boot images].

Expand All @@ -504,9 +523,9 @@ For more information, see xref:../machine_configuration/mco-coreos-layering.adoc

When {image-mode-os-lower} is configured, there are improvements to error reporting including the following changes:

* In certain scenarios after the custom layered image has been built and pushed, errors could cause the build process to fail. If this happens, the MCO now reports the errors and the `machineosbuild` object and builder pod are reported as failed.
* In certain scenarios after the custom layered image has been built and pushed, errors could cause the build process to fail. If this happens, the MCO now reports the errors and the `machineosbuild` object and builder pod are reported as failed.

* The `oc describe mcp` output has a new `ImageBuildDegraded` status field that reports if a custom layered image build has failed.
* The `oc describe mcp` output has a new `ImageBuildDegraded` status field that reports if a custom layered image build has failed.

[id="ocp-release-notes-machine-config-operator-cert-changes_{context}"]
==== Setting the kernel type parameter is now supported on {image-mode-os-on-lower} nodes
Expand All @@ -521,9 +540,9 @@ In clusters with slow, unreliable connections to an image registry, you can use
[id="ocp-release-notes-machine-config-operator-mcn_{context}"]
==== Improved MCO state reporting is now generally available

The machine config nodes custom resource, which you can use to monitor the progress of machine configuration updates to nodes, is now generally available.
The machine config nodes custom resource, which you can use to monitor the progress of machine configuration updates to nodes, is now generally available.

You can now view the status of updates to custom machine config pools in addition to the control plane and worker pools. The functionality for the feature has not changed. However, some of the information in the command output and in the status fields in the `MachineConfigNode` object has been updated. The `must-gather` for the Machine Config Operator now includes all `MachineConfigNodes` objects in the cluster. For more information, see xref:../machine_configuration/index.adoc#checking-mco-node-status_machine-config-overview[About checking machine config node status].
You can now view the status of updates to custom machine config pools in addition to the control plane and worker pools. The functionality for the feature has not changed. However, some of the information in the command output and in the status fields in the `MachineConfigNode` object has been updated. The `must-gather` for the Machine Config Operator now includes all `MachineConfigNodes` objects in the cluster. For more information, see xref:../machine_configuration/index.adoc#checking-mco-node-status_machine-config-overview[About checking machine config node status].

[id="ocp-release-notes-machine-management_{context}"]
=== Machine management
Expand Down Expand Up @@ -653,7 +672,7 @@ Support for sigstore `ClusterImagePolicy` and `ImagePolicy` objects is now gener

[NOTE]
====
The default `openshift` cluster image policy is Technology Preview and is active only in clusters that have enabled Technology Preview features.
The default `openshift` cluster image policy is Technology Preview and is active only in clusters that have enabled Technology Preview features.
====

[id="ocp-release-notes-machine-config-operator-sigtore-pki_{context}"]
Expand All @@ -674,14 +693,14 @@ By using the in-place pod resizing feature, you can apply a resize policy to cha
[id="ocp-release-notes-machine-config-operator-mount-oci_{context}"]
==== Mounting an OCI image into a pod

You can you use an image volume to mount an Open Container Initiative (OCI)-compliant container image or artifact directly into a pod.
You can you use an image volume to mount an Open Container Initiative (OCI)-compliant container image or artifact directly into a pod.

// Activate link when assembly/module is available: For more information, see ../nodes/pods/nodes-pods-image-volume.adoc#odes-pods-image-volume[Mounting an OCI image into a pod].

[id="ocp-release-notes-machine-config-operator-allocate-gpu_{context}"]
==== Allocating specific GPUs to pods (Technology Preview)

You can now enable pods to request GPUs based on specific device attributes, such as product name, GPU memory capacity, compute capability, vendor name, and driver version. These attributes are exposed by the by using a third-party DRA resource driver that you install.
You can now enable pods to request GPUs based on specific device attributes, such as product name, GPU memory capacity, compute capability, vendor name, and driver version. These attributes are exposed by the by using a third-party DRA resource driver that you install.

// Activate link when assembly/module is available: For more information, see /nodes/pods/nodes-pods-allocate-dra.adoc#nodes-pods-allocate-dra[Allocating GPUs to pods].

Expand Down