Cherrypick #4144: fix cannot access ResourceRegistry with its singularName

[XiShanYongYe-Chang]

Which PR needs cherry-picks:

PR #4144

Which release branches need this patch:

• release-1.7 Automated cherry pick of #4144: fix: cannot access ResourceRegistry with its singularName #4153
• release-1.6 Automated cherry pick of #4144: fix: cannot access ResourceRegistry with its singularName #4157
• release-1.5 Automated cherry pick of #4144: fix: cannot access ResourceRegistry with its singularName #4155

How to cherry-pick PRs:

The hack/cherry_pick_pull.sh script can help you initiate a cherry-pick
automatically, please follow the instructions at this guideline.

The script will send the PR for you, please remember copy the release notes from
the original PR by to the new PR description part.

How to join or take the task:

Just reply on the issue with the message /assign in a separate line.

Then, the issue will be assigned to you.

Useful References:

• Release timeline: https://karmada.io/docs/releases
• How to cherry-pick PRs: https://karmada.io/docs/contributor/cherry-picks

Anything else we need to know:

[Yan-Daojiang]

/assign

[RainbowMango]

@XiShanYongYe-Chang
release-1.5 and release-1.6 aren't affected by this bug. (I tested against v1.5.4, there is no problem.)

This bug was introduced by #3730 when we updated Kubernetes dependencies to v1.27. So, we only need to fix it at release-1.7 and master.

There is no side-effect checking them to release-1.5 and release-1.6 though.

[XiShanYongYe-Chang]

@RainbowMango Ok, thanks

This bug was introduced by #3730

I'd like to know how this is confirmed.

[XiShanYongYe-Chang]

/close

[karmada-bot]

@XiShanYongYe-Chang: Closing this issue.

In response to this:

/close

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.