Bug 2043801 - Bump CoreDNS to k8s.io/api 1.23
Summary: Bump CoreDNS to k8s.io/api 1.23
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Networking
Version: 4.10
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.10.0
Assignee: Miciah Dashiel Butler Masters
QA Contact: Shudi Li
Depends On:
TreeView+ depends on / blocked
Reported: 2022-01-22 02:18 UTC by Miciah Dashiel Butler Masters
Modified: 2022-08-04 22:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2022-03-10 16:41:47 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github openshift coredns pull 70 0 None open Bug 2043801: Merge 1.8.7 2022-01-22 02:52:21 UTC
Red Hat Product Errata RHSA-2022:0056 0 None None None 2022-03-10 16:42:03 UTC

Description Miciah Dashiel Butler Masters 2022-01-22 02:18:04 UTC
Description of problem:

The current version of openshift/coredns vendors Kubernetes 1.21 packages.  OpenShift 4.10 is based on Kubernetes 1.23.  

OpenShift release version:


Steps to Reproduce (in detail):

1. Check <https://github.com/openshift/coredns/blob/release-4.10/go.mod>.

Actual results:

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

Expected results:

Kubernetes packages are at version v0.23.0.

Impact of the problem:

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

Additional info:

The release-4.10 branch of the github.com/openshift/coredns repository is based on upstream github.com/coredns/coredns version 1.8.4.  Upstream CoreDNS moved to Kubernetes 1.23 in its 1.8.7 release (cf. <https://github.com/coredns/coredns/compare/v1.8.6...v1.8.7>).

Comment 3 Shudi Li 2022-01-27 01:36:46 UTC
This bug has been fixed.

Check <https://github.com/openshift/coredns/blob/release-4.10/go.mod>, Kubernetes packages (k8s.io/api, k8s.io/apimachinery, and k8s.io/client-go) are at version v0.23.1:

38	k8s.io/api v0.23.1
39	k8s.io/apimachinery v0.23.1
40	k8s.io/client-go v0.23.1
41	k8s.io/klog/v2 v2.40.1

Comment 4 Shudi Li 2022-01-27 12:17:28 UTC
Verified it with 4.10.0-0.nightly-2022-01-26-234447

% oc get clusterversion
NAME      VERSION                              AVAILABLE   PROGRESSING   SINCE   STATUS
version   4.10.0-0.nightly-2022-01-26-234447   True        False         57m     Cluster version is 4.10.0-0.nightly-2022-01-26-234447

% oc -n openshift-dns get pods
NAME                  READY   STATUS    RESTARTS   AGE
dns-default-ddxgt     2/2     Running   0          77m
dns-default-fw5xp     2/2     Running   0          67m
dns-default-gkhgj     2/2     Running   0          77m
dns-default-p8gwx     2/2     Running   0          77m
dns-default-qkc6h     2/2     Running   0          63m
dns-default-xmk4m     2/2     Running   0          66m
node-resolver-4nb24   1/1     Running   0          77m
node-resolver-5kdt4   1/1     Running   0          77m
node-resolver-bvvn9   1/1     Running   0          77m
node-resolver-q5zc8   1/1     Running   0          64m
node-resolver-zkfwb   1/1     Running   0          68m
node-resolver-zrx5v   1/1     Running   0          68m

% oc -n openshift-dns rsh dns-default-ddxgt 
Defaulted container "dns" out of: dns, kube-rbac-proxy
sh-4.4# coredns -version
linux/amd64, go1.17.2, 

Comment 7 errata-xmlrpc 2022-03-10 16:41:47 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.