1.18 conformance fails because coredns does not create pod A records

Bug #1875979 reported by George Kraft
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
CDK Addons
Fix Released
Undecided
George Kraft

Bug Description

DNS conformance tests fail on Charmed Kubernetes 1.18:

[Fail] [sig-network] DNS [It] should provide DNS for services [Conformance]
[Fail] [sig-network] DNS [It] should provide /etc/hosts entries for the cluster [LinuxOnly]
[Fail] [sig-network] DNS [It] should resolve DNS of partial qualified names for services
[Fail] [sig-network] DNS [It] should provide DNS for pods for Hostname [LinuxOnly] [Conformance]
[Fail] [sig-network] DNS [It] should provide DNS for the cluster [Conformance]
[Fail] [sig-network] DNS [It] should provide DNS for pods for Subdomain [Conformance]

The tests time out, repeatedly hitting this error:

Unable to read wheezy_udp@PodARecord from pod dns-3865/dns-test-bdcc60f7-bc74-45cb-8ad2-be3605413c92: the server could not find the requested resource (get pods dns-test-bdcc60f7-bc74-45cb-8ad2-be3605413c92)
Unable to read wheezy_tcp@PodARecord from pod dns-3865/dns-test-bdcc60f7-bc74-45cb-8ad2-be3605413c92: the server could not find the requested resource (get pods dns-test-bdcc60f7-bc74-45cb-8ad2-be3605413c92)
Unable to read jessie_udp@PodARecord from pod dns-3865/dns-test-bdcc60f7-bc74-45cb-8ad2-be3605413c92: the server could not find the requested resource (get pods dns-test-bdcc60f7-bc74-45cb-8ad2-be3605413c92)
Unable to read jessie_tcp@PodARecord from pod dns-3865/dns-test-bdcc60f7-bc74-45cb-8ad2-be3605413c92: the server could not find the requested resource (get pods dns-test-bdcc60f7-bc74-45cb-8ad2-be3605413c92)
Lookups using dns-3865/dns-test-bdcc60f7-bc74-45cb-8ad2-be3605413c92 failed for: [wheezy_udp@PodARecord wheezy_tcp@PodARecord jessie_udp@PodARecord jessie_tcp@PodARecord]

The test is able to hit the dns-3865/dns-test-bdcc60f7-bc74-45cb-8ad2-be3605413c92 pod just fine, but it's getting 404 from the pod trying to access its PodARecord lookup results.

Those results are missing because the lookup fails. CoreDNS is not creating pod A records based on IP (e.g. 10-1-13-3.default.pod.cluster.local). Indeed, this is disabled in the default configuration of CoreDNS. See the `pods` config documented here: https://github.com/coredns/coredns/blob/5347bc38e733a0ff084aafe7713d24903596f440/plugin/kubernetes/README.md

Revision history for this message
George Kraft (cynerva) wrote :
George Kraft (cynerva)
Changed in cdk-addons:
assignee: nobody → George Kraft (cynerva)
status: New → Incomplete
status: Incomplete → In Progress
George Kraft (cynerva)
Changed in cdk-addons:
milestone: none → 1.18+ck1
Revision history for this message
George Kraft (cynerva) wrote :
tags: added: review-needed
Changed in cdk-addons:
status: In Progress → Fix Committed
tags: removed: review-needed
Revision history for this message
George Kraft (cynerva) wrote :
Changed in cdk-addons:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.