Bug 2090827
Summary: | Rebase CoreDNS to 1.9.2 and k8s 1.24 | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Miciah Dashiel Butler Masters <mmasters> |
Component: | Networking | Assignee: | Miciah Dashiel Butler Masters <mmasters> |
Networking sub component: | DNS | QA Contact: | Melvin Joseph <mjoseph> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | high | ||
Priority: | high | CC: | hongli |
Version: | 4.11 | ||
Target Milestone: | --- | ||
Target Release: | 4.11.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Release Note | |
Doc Text: |
Wildcard queries (that is, queries that include the label "*" or the label "any") for names within the cluster.local domain are deprecated. Such queries still resolve in OpenShift 4.11 as they do in earlier OpenShift versions, but these queries may not resolve in later versions of OpenShift. On OpenShift 4.10 and 4.11 clusters, you can check whether clients are using wildcard queries by looking for log messages containing the phrase "deprecated wildcard queries received" in the "dns" container of the "dns-default" pods in the "openshift-dns" namespace. For example:
% oc --namespace=openshift-dns logs --container=dns --selector=dns.operator.openshift.io/daemonset-dns=default --tail=-1 --max-log-requests=6 | grep -e 'deprecated wildcard queries received' -m1
[WARNING] plugin/kubernetes: 1 deprecated wildcard queries received. Wildcard queries will no longer be supported in the next minor release.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2022-08-10 11:14:36 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Miciah Dashiel Butler Masters
2022-05-26 15:57:33 UTC
melvinjoseph@mjoseph-mac Downloads % oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.11.0-0.ci.test-2022-05-30-150908-ci-ln-xfrkp2b-latest True False 51m Cluster version is 4.11.0-0.ci.test-2022-05-30-150908-ci-ln-xfrkp2b-latest melvinjoseph@mjoseph-mac Downloads % melvinjoseph@mjoseph-mac Downloads % melvinjoseph@mjoseph-mac Downloads % melvinjoseph@mjoseph-mac Downloads % melvinjoseph@mjoseph-mac Downloads % oc version Client Version: 4.10.10 Server Version: 4.11.0-0.ci.test-2022-05-30-150908-ci-ln-xfrkp2b-latest Kubernetes Version: v1.24.0-alpha.3.3613+01aa0f3f6052c9-dirty melvinjoseph@mjoseph-mac Downloads % oc get pod -n openshift-dns NAME READY STATUS RESTARTS AGE dns-default-24sk4 2/2 Running 0 67m dns-default-42qtf 2/2 Running 0 61m dns-default-f5cdr 2/2 Running 0 67m dns-default-hcthw 2/2 Running 0 67m dns-default-kkmdc 2/2 Running 0 60m node-resolver-6bbpq 1/1 Running 0 61m node-resolver-fgkgr 1/1 Running 0 67m node-resolver-gfjv6 1/1 Running 0 61m node-resolver-k9btf 1/1 Running 0 67m node-resolver-lr54t 1/1 Running 0 67m node-resolver-vvmhs 1/1 Running 0 61m melvinjoseph@mjoseph-mac Downloads % oc rsh -n openshift-dns dns-default-24sk4 Defaulted container "dns" out of: dns, kube-rbac-proxy sh-4.4# coredns --version CoreDNS-1.9.2 linux/amd64, go1.18, sh-4.4# exit exit melvinjoseph@mjoseph-mac Downloads % Hence verified 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 (Important: OpenShift Container Platform 4.11.0 bug fix and 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. https://access.redhat.com/errata/RHSA-2022:5069 |