chore: let kube version of artifaces/deploy/karmada-apiserver versionsupport configuration.

[liangyuanpeng]

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

The workflow of APIServer compatibility is failing when it's running with master, see

• [WIP] chore: APIServer compatibility for master #4898
• https://github.com/karmada-io/karmada/actions/runs/8950239870/job/24585393557

The reason is master is running with karmada-apiserver v1.27.11, and the workflow of APIServer compatibility is change the version of karmada-apiserver by patching karmada-apiserver, and actually it's happening the downgrade/upgrade of karmada-apiserver, it's always failing if karmada-apiserver have add some new API. For now, it's flowcontrol.apiserver.k8s.io/v1beta3,
available with v1.26, so it will always failed if karmada-apiserver downgrade to lessthan v1.26

So this PR is working for useing environment to config the karmada-apiserver version, Avoid karmada-apiserver downgrade/upgrade happening.

Which issue(s) this PR fixes:
Fixes #

Special notes for your reviewer:

This PR CI is failing with the confict artifact name, will resolve by #4897

Does this PR introduce a user-facing change?:

[codecov-commenter]

Codecov Report

All modified and coverable lines are covered by tests ✅

Project coverage is 53.14%. Comparing base (a8697ec) to head (9a32daa).
Report is 2 commits behind head on master.

❗ Your organization needs to install the Codecov GitHub app to enable full functionality.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #4899      +/-   ##
==========================================
+ Coverage   53.12%   53.14%   +0.01%     
==========================================
  Files         251      251              
  Lines       20415    20415              
==========================================
+ Hits        10845    10849       +4     
+ Misses       8856     8853       -3     
+ Partials      714      713       -1     

Flag	Coverage Δ
unittests	53.14% <ø> (+0.01%)	⬆️

Flags with carried forward coverage won't be shown. Click here to find out more.

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

[RainbowMango]

cc @zhzhuang-zju

[zhzhuang-zju]

Thanks for your important commit! Review is ongoing, and my viewpoint just for reference only.

[zhzhuang-zju]

@liangyuanpeng By looking at the logs uploaded by CI, I found that the versions of karmada-apiserver are both v1.25.4 and have not changed based on the configured environment variables. Can you help confirm this?

[liangyuanpeng]

we need to cherry pick this change to branch of release, and then it can be working for release branch, i update the trigger branch to master for verify.

[zhzhuang-zju]

we need to cherry pick this change to branch of release, a

Yes, changes to files karmada-apiserver.yaml, kube-controller-manager.yamland deploy-karmada.sh should be synchronized to previous release versions.

@liangyuanpeng It would be nice to have an issue to break down and track this task, which would also make the whole work clearer

[liangyuanpeng]

tracking at #4929

[liangyuanpeng]

Delete the changes of .github/workflows/ci-schedule-compatibility.yaml for clean cherrypick and leave it to the next PR.

[zhzhuang-zju]

thanks
/lgtm
cc @RainbowMango

[RainbowMango]

/assign

[RainbowMango]

/approve
I can tell with this patch, we can specify which kube-apiserver should be used during look up, and we don't need to update images afterwards

[RainbowMango]

Is there a plan to bump this to v1.28?

[liangyuanpeng]

yes, i will open a PR for it ASAP.

[RainbowMango]

Thanks.
I'm asking this because I guess the default version of karmadactl init/operator/chart might need to update as well.

[liangyuanpeng]

I hope that the default version of karmada-apiserver will be consistent with the version of the dependent go module (WDYT), and will catch up to be consistent ASAP.

[RainbowMango]

That's a good idea if you mean the version of the k8s.io/xxx dependencies in go.mod file.

[RainbowMango]

k8s.io/client-go version VS kube-apiserver version

[karmada-bot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: RainbowMango

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 [RainbowMango]

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