Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it.

Please note that we're already in Test Freeze for the release-1.35 branch. This means every merged PR will be automatically fast-forwarded via the periodic ci-fast-forward job to the release branch of the upcoming v1.35.0 release.

Fast forwards are scheduled to happen every 6 hours, whereas the most recent run was: Fri Dec 5 21:38:05 UTC 2025.

This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Welcome @mikecook!

It looks like this is your first PR to kubernetes/kubernetes 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes/kubernetes has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

Hi @mikecook. Thanks for your PR.

I'm waiting for a github.com 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.

[APPROVALNOTIFIER] This PR is NOT APPROVED

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

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

With these new tests, before the fix

% go test -v ./staging/src/k8s.io/apimachinery/third_party/forked/golang/reflect/       
=== RUN   TestEqualities
    deep_equal_test.go:96: DeepEqualWithNilDifferentFromEmpty: Expected (map[foo:1] == map[]) == false, but got true
    deep_equal_test.go:96: DeepEqualWithNilDifferentFromEmpty: Expected ([] == [1]) == false, but got true
    deep_equal_test.go:96: DeepEqualWithNilDifferentFromEmpty: Expected ([] == [1 2 3]) == false, but got true
    deep_equal_test.go:96: DeepEqualWithNilDifferentFromEmpty: Expected ([] == [1 2 3]) == false, but got true
    deep_equal_test.go:96: DeepEqualWithNilDifferentFromEmpty: Expected (map[] == map[foo:1]) == false, but got true
    deep_equal_test.go:96: DeepEqualWithNilDifferentFromEmpty: Expected ([1] == []) == false, but got true
    deep_equal_test.go:96: DeepEqualWithNilDifferentFromEmpty: Expected ([1 2 3] == []) == false, but got true
    deep_equal_test.go:96: DeepEqualWithNilDifferentFromEmpty: Expected ([1 2 3] == []) == false, but got true
    deep_equal_test.go:96: DeepEqualWithNilDifferentFromEmpty: Expected (map[foo:1] == map[]) == false, but got true
--- FAIL: TestEqualities (0.00s)