Loading...

XML

Word

Printable

Severity:
Critical
Regression:
None
Sprint:
Sprint 225
sprint_count:
1
Release Blocker:
Rejected
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Release Note Text:

Hide
* Previously, CoreDNS was based on kubernetes 1.24 while {product-title} 4.12 is based on kubernetes 1.25. With this update, CoreDNS is v1.10.0, new features have been added, and {product-title} 4.12 uses kubernetes 1.25 APIs. (link: https://issues.redhat.com/browse/OCPBUGS-1731[*~~OCPBUGS-1731~~*])

Show
* Previously, CoreDNS was based on kubernetes 1.24 while {product-title} 4.12 is based on kubernetes 1.25. With this update, CoreDNS is v1.10.0, new features have been added, and {product-title} 4.12 uses kubernetes 1.25 APIs. (link: https://issues.redhat.com/browse/OCPBUGS-1731 [* OCPBUGS-1731 *])
Release Note Type:
Bug Fix
Release Note Status:
Done
Target Version:

4.12.0

Description of problem:

The current version of openshift's corendns is based on Kubernetes 1.24 packages.  OpenShift 4.12 is based on Kubernetes 1.25.

Version-Release number of selected component (if applicable):

4.12

How reproducible:

Always

Steps to Reproduce:

1. Check https://github.com/openshift/coredns/blob/release-4.12/go.mod

Actual results:

Kubernetes packages (k8s.io/api, k8s.io/apimachinery, and k8s.io/client-go) are at version v0.24.0.

Expected results:

Kubernetes packages are at version v0.25.0 or later.

Additional info:

Using old Kubernetes API and client packages brings risk of API compatibility issues.

clones

OCPBUGS-1730 Bump openshift-router to k8s 1.25

links to

openshift/coredns#76: OCPBUGS-1731: Merge 1.10.0