CNCF dns tests are failing with context deadline exceeded errors

[kasturinarra]

Summarizing 3 Failures:
[FAIL] [sig-network] DNS [It] should provide DNS for pods for Subdomain [Conformance] [sig-network, Conformance]
k8s.io/kubernetes/test/e2e/network/dns_common.go:476
[FAIL] [sig-network] DNS [It] should provide DNS for services [Conformance] [sig-network, Conformance]
k8s.io/kubernetes/test/e2e/network/dns_common.go:476
[FAIL] [sig-network] DNS [It] should provide DNS for the cluster [Conformance] [sig-network, Conformance]
k8s.io/kubernetes/test/e2e/network/dns_common.go:476

Ran 423 of 7137 Specs in 7750.700 seconds
FAIL! -- 420 Passed | 3 Failed | 0 Pending | 6714 Skipped
--- FAIL: TestE2E (7750.95s)
FAIL

sonobuoy-results-arm64.zip

[coderabbitai]

📝 CodeRabbit Plan Mode

Generate an implementation plan and prompts that you can use with your favorite coding agent.

• Create Plan

Examples

• Example 1
• Example 2

---

🔗 Similar Issues

Possible Duplicates

• CNCF tests related to DNS are failing on microshift upstream builds #173

Related Issues

• The kindnet isolated test may be failing with run-healthy timeout #81

🔗 Related PRs

#180 - ISSUE-173: Fix CNCF host name resolution errors [closed]

👤 Suggested Assignees

• kasturinarra
• ggiguash

---

🧪 Issue enrichment is currently in open beta.

You can configure auto-planning by selecting labels in the issue_enrichment configuration.

To disable automatic issue enrichment, add the following to your .coderabbit.yaml:

issue_enrichment:
  auto_enrich:
    enabled: false

💬 Have feedback or questions? Drop into our discord!