multinode fails conformance test with kindnet (but calico works)

[azhao155]

Run the conformance test with default kindnet cni. Tests failed due to coreDNS can't resolve service name on the non-mater nodes.

Run the same test for calico cni for both docker and containerd runtime. All passed.

There are two things we could do:

1. Change default cni to a more lightweight one which pass all the conformance tests.
2. Investigate the kindnet dns issue.

The attachment are the tests log for calico with docker and containerd runtime.

e2e.log
e2e.log

[azhao155]

@medyagh
@sharifelgamal

[tstromberg]

I imagine that the CoreDNS issue might be that the non-master node can't access CoreDNS on the master.

I'd be open to switching CNI's if another works as well without a performance penalty.

Any movement on this?

[sharifelgamal]

I think we'd need to do some benchmarking with each of the passing CNI and figure out the best path forward that way. In addition, there was a PR (#9875) that will have probably fixed kindnet in general. We should rerun conformance with kindnet to double check.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[prezha]

i think this issue could be resolved by #10985 with kindnet cni