Conformance Test: some [sig-network] tests failed.

[MJ]

I have run conformance test (by sonobuoy) on my cluster and I have some failures. my kubernetes version is 1.18.3. I have run the tests many times and the result is the same all the time:
Plugin: e2e
Status: failed
Total: 4992
Passed: 266
Failed: 9
Skipped: 4717

Failed tests:
[sig-network] Services should be able to change the type from ClusterIP to ExternalName [Conformance]
[sig-network] DNS should provide DNS for ExternalName services [Conformance]
[sig-network] DNS should provide DNS for services [Conformance]
[sig-network] DNS should provide DNS for pods for Hostname [LinuxOnly] [Conformance]
[sig-network] Services should be able to change the type from NodePort to ExternalName [Conformance]
[sig-network] DNS should provide /etc/hosts entries for the cluster [LinuxOnly] [Conformance]
[sig-network] DNS should provide DNS for pods for Subdomain [Conformance]
[sig-network] DNS should provide DNS for the cluster [Conformance]
[sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]

what can cause these failures?

[zenhighzer]

same here,

8 x virtualbox-machines, each with two network-adapters (nat and host-only adapter):

• 1 x a dns-server/bind9 dns-lookups in generall are working fine between all vm´s
• 2 x loadbalancer-vm (haproxy: vip for control-plane-endpoint)
• running 3 x k8s-master-vm, 2 x k8s-worker-vm
• installed via. kubeadm and flannel

Plugin: e2e
Status: failed
Total: 5771
Passed: 329
Failed: 8
Skipped: 5434

Failed tests:
[sig-network] DNS should resolve DNS of partial qualified names for services [LinuxOnly] [Conformance]
[sig-network] DNS should provide /etc/hosts entries for the cluster [LinuxOnly] [Conformance]
[sig-network] DNS should provide DNS for pods for Hostname [LinuxOnly] [Conformance]
[sig-network] DNS should provide DNS for pods for Subdomain [Conformance]
[sig-network] DNS should provide DNS for the cluster [Conformance]
[sig-network] DNS should provide DNS for services [Conformance]
[sig-network] Services should be able to change the type from NodePort to ExternalName [Conformance]
[sig-network] Services should be able to change the type from ClusterIP to ExternalName [Conformance]

Plugin: systemd-logs
Status: passed
Total: 5
Passed: 5
Failed: 0
Skipped: 0

[MJ]

hi @zenhighzer
I think you have changed your default cluster domain name from cluster.local to some thing else.
you shoud run your cluster conformance test with an option switch by whitch you can specify your correct domain name to conformance test.
you can find the correct option (to tell the confomance test your correct domain name) from sonobuoy documents.

[hitorig]

hi @zenhighzer I think you have changed your default cluster domain name from cluster.local to some thing else. you shoud run your cluster conformance test with an option switch by whitch you can specify your correct domain name to conformance test. you can find the correct option (to tell the confomance test your correct domain name) from sonobuoy documents.

I set cluster domain name with cluster.local but it did not work

[Riaan Kleinhans]

Stale issue.
Sure we can close after 3 years of no action or follow-up.