cherry-picks: 4899 let kube version of artifaces/deploy/karmada-apiserver versionsupport configuration.

[liangyuanpeng]

Which PR needs cherry-picks:

PR #4899

PR is changing the files of artifacts/deploy and hack, it need to cherry pick the change to release branch and then it can be work for workflow APIServer compatibility

/assign

Which release branches need this patch:

• release-1.8 Automated cherry pick of #4899: chore: let kube version of artifaces/deploy/karmada-apiserver #5132
• release-1.9 Automated cherry pick of #4899: chore: let kube version of artifaces/deploy/karmada-apiserver #5133
• release-1.10 Automated cherry pick of #4899: chore: let kube version of artifaces/deploy/karmada-apiserver #5134

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:

[SkySingh04]

Hey is this issue still open? I would like to work on it

[liangyuanpeng]

@Akash-Singh04 ready to go, please feel free to pick it up :)

[SkySingh04]

/assign

[liangyuanpeng]

kindly ping @Akash-Singh04

[SkySingh04]

working on this, will be done by EOD

[SkySingh04]

@liangyuanpeng #5134 #5133 #5132 have been made, kindly review them and let me know if any further changes are required

[RainbowMango]

/close
as all tasks are done. thanks, @Akash-Singh04 for the effort.

[karmada-bot]

@RainbowMango: Closing this issue.

In response to this:

/close
as all tasks are done. thanks, @Akash-Singh04 for the effort.

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.