OCP 4.10 Release Notes Tracker

[stevsmit]

Please leave comments here for anything that should be highlighted in the 4.10 release notes. If possible, provide a link to the Jira or BZ related to your item. Thank you!

A note about migrating to Jira
This tracker might be moved to Jira. In the event that happens, I will update accordingly and provide a direct link.

A note about known issues
All Bugzilla items that need to be documented as known issues in the release notes should have Doc Type = Known Issue and the Doc Text field populated accordingly. Before adding a known issue to this tracker:

1. Ensure the Doc Type and Doc Text fields are filled in correctly.
2. See if your issue shows up in the query we will use to populate the release notes.
3. If the fields are set correctly, and the issue is not in the query, add it here.

Resources

• Feature GA Status Tracker

[atiratree]

added support for podman config credentials in oc

• oc commands that use registry config (oc login, oc image, etc.) now obtain credentials from podman config locations if a registry entry cannot be found in the default docker config location.
• The order can be changed via REGISTRY_AUTH_PREFERENCE env variable to docker (current default - deprecated) or podman (prioritizes podman credentials over docker).
• REGISTRY_AUTH_FILE env variable can be used instead of --registry-config option

Deprecated features

• docker config location deprecated in oc. oc commands that use registry config currently obtain credentials from docker config location (usually ~/.docker/config.json) by default. This is deprecated and will be removed in 2 releases in favor of podman config locations.
• --registry-config or --to option in oc registry login command will stop accepting empty files (non existing files will still be valid use case) and writing to - (stdout) is also deprecated

PRs: openshift/oc#893, openshift/oc#983 and openshift/oc#1011

[soltysh]

oc 4.10 is the last release being built with support for rhel7, starting from 4.11 we will provide only rhel8 compatible builds. This is coming from the fact that oc is statically linking glibc. More information can be found in https://developers.redhat.com/blog/2020/10/08/migrating-c-and-c-applications-from-red-hat-enterprise-linux-version-7-to-version-8#

[mtulio]

On AWS OpenShift Container Platform 4.10 will prefer m6i instance types when available on the region falling back to m5 types when they're not. The sizes will keep the same: m6i.xlarge for control-plane and m6.large for compute nodes.

• PR: aws-ec2: add m6i as preferred instance type installer#5327
• Card: https://issues.redhat.com/browse/SPLAT-329

The default block storage provisioned by the installer on AWS nodes was changed from gp2 to gp3

• PR: aws: changing default EBS type on masters to gp3. installer#5239
• Cards: SPLAT-253 SPLAT-343

[ptrnull]

The release notes indicate that OpenShift 4.10 is released based on Kubernetes 1.22 but the FC release is using Kubernetes 1.23: https://openshift-release-artifacts.apps.ci.l2s4.p1.openshiftapps.com/4.10.0-fc.1/release.txt

[ctauchen] Updates for Kubernetes 1.23 are in the RN: https://docs.openshift.com/container-platform/4.10/release_notes/ocp-4-10-release-notes.html#ocp-4-10-about-this-release

[s-urbaniak]

Starting from OpenShift 4.10 control plane components have no fallback mechanisms included any more to fall back to the Common Name field on X.509 certificates when no Subject Alternative Names (SANs) are present. Any certificates must properly set the Subject Alternative Names field. This was initially announced in OpenShift 4.6, see https://docs.openshift.com/container-platform/4.6/release_notes/ocp-4-6-release-notes.html#ocp-4-6-tls-common-name.

[ctauchen] Added here: #41821

[SNiemann15]

Working together with @ktania46 and @alishaIBM to add IBM Z and Power content to the RNs:
https://docs.google.com/document/d/1LZqUJ86zmUt2Erh1mjhrACEbfBHEoE4z2Hgnr_MrugU/edit#heading=h.gi343gic2seb

PR for P/Z #40806

[jechen0648]

EgressIP on plubic cloud: https://issues.redhat.com/browse/SDN-1316 https://issues.redhat.com/browse/SDN-1315, https://issues.redhat.com/browse/SDN-1332,

[ctauchen] RN here: #39805

[duanwei33]

Strorge part:
CSI Azure Disk Driver Operator GA in 4.10 https://issues.redhat.com/browse/STOR-552
CSI OpenStack Cinder Driver Operator GA from 4.8 https://issues.redhat.com/browse/STOR-679
CSI AWS EFS Driver Operator GA in 4.10 https://issues.redhat.com/browse/STOR-362
CSI vSphere Driver Operator GA in 4.10 https://issues.redhat.com/browse/STOR-558
CSI Alicloud Disk operator GA in 4.10 https://issues.redhat.com/browse/STOR-574
CSI IBM Cloud Operator GA in 4.10 https://issues.redhat.com/browse/STOR-598
CSI Azure File Operator TP in 4.10 https://issues.redhat.com/browse/STOR-555
Automatic device discovery and provisioning with Local Storage Operator TP in 4.10

[rioliu-rh]

for config drift part, if pr#2910 cannot be merged before code freeze date Jan 28, we need to add bz2038240 to release notes as known issue

[quarterpin]

The ingress now adds support for IBM cloud environment: https://issues.redhat.com/browse/NE-619
The telemetry now includes metrics to track the number of active NLB routers in an AWS environment: https://issues.redhat.com/browse/NE-704

[xingxingxia]

1 PodSecurity is temporarily disabled in 4.10 and will be enabled in 4.11, see bug 2008462 . It is promoted to beta in 1.23, and 4.10 is k8s 1.23, so we can mention this (Discussed with Dev in Slack).
2 Add notes for OpenID IDP group consumption AUTH-8

[rioliu-rh]

for config drift part, if pr#2910 cannot be merged before code freeze date Jan 28, we need to add bz2038240 to release notes as known issue

PR is merged and BZ is verified. don't need to add it to release notes

[gpei]

For Installation in 4.10

• Allow thin provisioning for VMware vSphere IPI - https://issues.redhat.com/browse/CORS-1674
• Azure: IPI Support for Azure Stack Hub - https://issues.redhat.com/browse/CORS-1596
• IBM Public Cloud: Support IPI deployment - https://issues.redhat.com/browse/CORS-1513
• Support Alibaba IPI installer - https://issues.redhat.com/browse/SPLAT-193

[bgilbert]

coreos-installer now has iso customize and pxe customize commands for flexible customization of bare metal RHCOS installation from the live ISO/PXE images (COS-823).