-
Notifications
You must be signed in to change notification settings - Fork 891
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
chore: let kube version of artifaces/deploy/karmada-apiserver versionsupport configuration. #4899
chore: let kube version of artifaces/deploy/karmada-apiserver versionsupport configuration. #4899
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
❗ 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
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
11b00c4
to
c4bbedf
Compare
c4bbedf
to
3273fde
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks for your important commit! Review is ongoing, and my viewpoint just for reference only.
@liangyuanpeng By looking at the logs uploaded by CI, I found that the versions of |
3273fde
to
a75277a
Compare
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. |
Yes, changes to files @liangyuanpeng It would be nice to have an issue to break down and track this task, which would also make the whole work clearer |
tracking at #4929 |
45e349a
to
771e331
Compare
… support configuration. Signed-off-by: Lan Liang <gcslyp@gmail.com>
771e331
to
8e43753
Compare
Delete the changes of |
thanks |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/assign
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
/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
@@ -200,8 +200,10 @@ fi | |||
# deploy karmada apiserver | |||
TEMP_PATH_APISERVER=$(mktemp -d) | |||
trap '{ rm -rf ${TEMP_PATH_APISERVER}; }' EXIT | |||
KARMADA_APISERVER_VERSION=${KARMADA_APISERVER_VERSION:-"v1.27.11"} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there a plan to bump this to v1.28?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
yes, i will open a PR for it ASAP.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks.
I'm asking this because I guess the default version of karmadactl init
/operator
/chart
might need to update as well.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
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.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
That's a good idea if you mean the version of the k8s.io/xxx
dependencies in go.mod file.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
k8s.io/client-go version VS kube-apiserver version
[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:
Approvers can indicate their approval by writing |
…#4899-upstream-release-1.8 Automated cherry pick of #4899: chore: let kube version of artifaces/deploy/karmada-apiserver
…#4899-upstream-release-1.10 Automated cherry pick of #4899: chore: let kube version of artifaces/deploy/karmada-apiserver
…deploy/karmada-apiserver (#5133) * chore: let kube version of artifaces/deploy/karmada-apiserver version support configuration. Signed-off-by: Lan Liang <gcslyp@gmail.com> * Updated version in deploy-karmadda.sh Signed-off-by: Akash Singh <akashsingh2210670@gmail.com> --------- Signed-off-by: Lan Liang <gcslyp@gmail.com> Signed-off-by: Akash Singh <akashsingh2210670@gmail.com> Co-authored-by: Lan Liang <gcslyp@gmail.com>
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
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'sflowcontrol.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?: