bump coredns version to 1.10.1

[eminaktas]

What type of PR is this?

Uncomment only one /kind <> line, hit enter to put that in a new line, and remove leading whitespaces from that line:

/kind api-change
/kind bug
/kind cleanup
/kind design
/kind documentation
/kind failing-test
/kind feature
/kind flake

/kind feature

What this PR does / why we need it:

bumps coredns default version to 1.10.1

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?:

bump coredns version to 1.10.1

[k8s-ci-robot]

Hi @eminaktas. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[floryut]

@eminaktas Thank you!
I'm putting a hold, as we might want to wait for 1.27 switch, WDYT ?
On the other hand as long as CI works, no need to wait I guess.

/hold

[eminaktas]

@eminaktas Thank you! I'm putting a hold, as we might want to wait for 1.27 switch, WDYT ? On the other hand as long as CI works, no need to wait I guess.

/hold

Thanks. CI failed :(. I'll take a look 👍

[eminaktas]

/retest

[k8s-ci-robot]

@eminaktas: Cannot trigger testing until a trusted user reviews the PR and leaves an /ok-to-test message.

In response to this:

/retest

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[eminaktas]

When I checked the logs nodelocaldns was not able to reach coredns.

[ERROR] plugin/errors: 2 netchecker-service.cluster.local. AAAA: dial tcp 10.233.0.3:53: connect: connection refused
[ERROR] plugin/errors: 2 netchecker-service.cluster.local. A: dial tcp 10.233.0.3:53: connect: connection refused
[ERROR] plugin/errors: 2 netchecker-service.cluster.local. AAAA: dial tcp 10.233.0.3:53: connect: connection refused
[ERROR] plugin/errors: 2 netchecker-service.894123319-4440306518.svc.cluster.local. A: dial tcp 10.233.0.3:53: connect: connection refused
[ERROR] plugin/errors: 2 netchecker-service.894123319-4440306518.svc.cluster.local. AAAA: dial tcp 10.233.0.3:53: connect: connection refused
[ERROR] plugin/errors: 2 netchecker-service.894123319-4440306518.svc.cluster.local. A: dial tcp 10.233.0.3:53: connect: connection refused
[ERROR] plugin/errors: 2 netchecker-service.894123319-4440306518.svc.cluster.local. AAAA: dial tcp 10.233.0.3:53: connect: connection refused

However, coredns pods look healthy and in the running state.

TASK [Check connectivity with all netchecker agents] ***************************
task path: /builds/kargo-ci/kubernetes-sigs-kubespray/tests/testcases/040_check-network-adv.yml:157
Thursday 08 June 2023  18:10:04 +0000 (0:00:00.199)       0:03:20.301 ********* 
fatal: [instance-2 -> instance-1(172.30.76.118)]: FAILED! => {
    "assertion": "agents_check_result is defined",
    "changed": false,
    "evaluated_to": false,
    "msg": "Connectivity check to netchecker agents failed"
}

[yankay]

/ok-to-test

[eminaktas]

Hey @floryut, I think it is ok to merge now. 👀

[floryut]

Hey @floryut, I think it is ok to merge now. 👀

Fine for me, as long as someone lgtm this
/unhold

[MrFreezeex]

Thanks for your contribution 👍!
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: eminaktas, floryut, MrFreezeex

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [floryut]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment