NE-2790: Update CoreDNS to v1.14.4 and Kubernetes 1.35

[aswinsuryan]

1. Why is this pull request needed and what does it do?

• Update CoreDNS version from 1.13.1 to 1.14.4
• Update Kubernetes dependencies from v0.34.1 to v0.35.4:
• k8s.io/api
• k8s.io/apimachinery
• k8s.io/client-go
• Update vendor directory with new dependencies

2. Which issues (if any) are related?

https://redhat.atlassian.net/browse/NE-2790

3. Which documentation changes (if any) need to be made?

4. Does this introduce a backward incompatible change or deprecation?

Summary by CodeRabbit

• Chores
  • Updated the core version to 1.14.4.
  • Refreshed several Go dependencies, including Kubernetes-related packages and YAML/CLI utilities, to newer versions.
  • Removed a couple of unused test-only dependencies.

[openshift-ci]

Skipping CI for Draft Pull Request.
If you want CI signal for your change, please convert it to an actual PR.
You can still manually trigger a test run with /test all

[openshift-ci-robot]

@aswinsuryan: This pull request references NE-2790 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "5.0.0" version, but no target version was set.

Details

In response to this:

1. Why is this pull request needed and what does it do?

• Update CoreDNS version from 1.13.1 to 1.14.4
• Update Kubernetes dependencies from v0.34.1 to v0.35.4:
• k8s.io/api
• k8s.io/apimachinery
• k8s.io/client-go
• Update vendor directory with new dependencies

2. Which issues (if any) are related?

https://redhat.atlassian.net/browse/NE-2790

3. Which documentation changes (if any) need to be made?

4. Does this introduce a backward incompatible change or deprecation?

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 openshift-eng/jira-lifecycle-plugin repository.

[openshift-ci]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign candita for approval. For more information see the Code Review Process.

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

Details

Needs approval from an approver in each of these files:

• OWNERS

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

[coderabbitai]

Walkthrough

This PR updates the exported CoreVersion constant from "1.13.1" to "1.14.4" in coremain/version.go, and bumps several Go module dependencies in go.mod, including Kubernetes packages (v0.34.1 to v0.35.4) and various indirect dependencies.

Changes

Version and Dependency Updates

Layer / File(s)	Summary
Core version bump coremain/version.go	CoreVersion constant updated from "1.13.1" to "1.14.4".
Dependency version bumps go.mod	Kubernetes packages (k8s.io/api, k8s.io/apimachinery, k8s.io/client-go) upgraded from v0.34.1 to v0.35.4; indirect dependencies (github.com/Masterminds/semver/v3, github.com/spf13/pflag, go.yaml.in/yaml/v2, gopkg.in/evanphx/json-patch.v4, k8s.io/kube-openapi, k8s.io/utils, sigs.k8s.io/json) updated; github.com/onsi/ginkgo/v2 and github.com/onsi/gomega removed from indirect requires.

Estimated code review effort: 1 (Trivial) | ~5 minutes

🚥 Pre-merge checks | ✅ 15

✅ Passed checks (15 passed)

Check name	Status	Explanation
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.
Linked Issues check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Out of Scope Changes check	✅ Passed	Check skipped because no linked issues were found for this pull request.
Stable And Deterministic Test Names	✅ Passed	No *_test.go files changed in the PR, so there are no Ginkgo titles to check for stability.
Test Structure And Quality	✅ Passed	No Ginkgo or other test files are changed; the PR only updates version/dependencies/vendor content, so the test-structure check is not applicable.
Microshift Test Compatibility	✅ Passed	No new non-vendor Ginkgo/e2e tests were added; the diff only changes version.go, go.mod, and go.sum with no MicroShift-sensitive test code.
Single Node Openshift (Sno) Test Compatibility	✅ Passed	Diff touches version/dependency/vendor files only; no _test.go files changed, so no new Ginkgo e2e tests to vet for SNO.
Topology-Aware Scheduling Compatibility	✅ Passed	Only version and dependency/vendor bumps changed; no manifests, controllers, or pod scheduling logic were modified.
Ote Binary Stdout Contract	✅ Passed	No changed process-level code writes to stdout; print hits are pflag docs/examples, and touched init/setup paths only register schemes/config.
Ipv6 And Disconnected Network Test Compatibility	✅ Passed	Diff is version/dependency/vendor-only; no new Ginkgo e2e tests or IPv4/external-network assumptions were added.
No-Weak-Crypto	✅ Passed	Diff only updates version/deps; exact scan found no added MD5/SHA1/DES/RC4/ECB or unsafe secret-compare code.
Container-Privileges	✅ Passed	PR only updates version/go.mod/go.sum/vendor; no container/K8s manifests or privilege settings were changed.
No-Sensitive-Data-In-Logs	✅ Passed	New klog calls log plugin names, watcher types, and taint values only; no passwords, tokens, PII, or internal hostnames are exposed.
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly matches the main changes: CoreDNS was updated to v1.14.4 and Kubernetes dependencies were bumped to 1.35-related versions.

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[gcs278]

/assign @bentito

[gcs278]

/assign @gcs278

[openshift-ci]

@aswinsuryan: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/e2e-gcp-serial-2of2	8827209	link	true	/test e2e-gcp-serial-2of2
ci/prow/unit	8827209	link	true	/test unit

Full PR test history. Your PR dashboard.

Details

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-sigs/prow repository. I understand the commands that are listed here.

[gcs278]

@aswinsuryan I think there is a misunderstanding - coredns is not a vendor bump, it's a full rebase. This is a fork of the coredns repo, so we need to a git rebase onto CoreDNS's 1.14.4 repo. Please follow #118 or #157 or #160 as examples.

I also started the /rebase AI skill here: #161, but never quite got it ironed out.

My only request (which btw slightly differs from the way @bentito did it in #157 ) is to keep the carry-patches after the merge commit, so that a script/AI tool can easily identify carry patches (otherwise, it's really tricky to find the difference between a rebased commit and a cherry-pick) like this:

Let me know if you have any questions.