-
Notifications
You must be signed in to change notification settings - Fork 911
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
local up: use karmadactl register to register pull mode cluster #5763
base: master
Are you sure you want to change the base?
Conversation
/hold for #5429 |
Codecov ReportAttention: Patch coverage is
❗ Your organization needs to install the Codecov GitHub app to enable full functionality. Additional details and impacted files@@ Coverage Diff @@
## master #5763 +/- ##
=======================================
Coverage 48.23% 48.24%
=======================================
Files 664 664
Lines 54749 54757 +8
=======================================
+ Hits 26410 26415 +5
- Misses 26624 26628 +4
+ Partials 1715 1714 -1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
20bc3b1
to
7d739d5
Compare
/hold cancel |
7d739d5
to
c79b668
Compare
/retest |
Signed-off-by: zhzhuang-zju <[email protected]>
Signed-off-by: zhzhuang-zju <[email protected]>
febf440
to
20d3f6a
Compare
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
/hold wait for #5970 With the results of e2e, the permission minimization of the pull mode cluster does not affect the basic functionality of |
@@ -74,7 +74,11 @@ ${KARMADACTL_BIN} join --karmada-context="${KARMADA_APISERVER_CLUSTER_NAME}" ${M | |||
"${REPO_ROOT}"/hack/deploy-scheduler-estimator.sh "${MAIN_KUBECONFIG}" "${HOST_CLUSTER_NAME}" "${MEMBER_CLUSTER_KUBECONFIG}" "${MEMBER_CLUSTER_2_NAME}" | |||
|
|||
# step4. register pull mode member clusters and install scheduler-estimator | |||
"${REPO_ROOT}"/hack/deploy-agent-and-estimator.sh "${MAIN_KUBECONFIG}" "${HOST_CLUSTER_NAME}" "${MAIN_KUBECONFIG}" "${KARMADA_APISERVER_CLUSTER_NAME}" "${MEMBER_CLUSTER_KUBECONFIG}" "${PULL_MODE_CLUSTER_NAME}" |
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.
Overall LGTM, but this seems to mean that we will lose control of /hack/ deploy-agent-and-estimater.sh
, i.e. the script may become obsolete without anyone knowing because it is not used in CI.
or we have any plan to remove /hack/ deploy-agent-and-estimater.sh
?
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.
Hi, long time no see 😄
nice catch, I'll add this in #5916
What type of PR is this?
/kind feature
What this PR does / why we need it:
Currently,
local-up-karmada
uses script to deploykarmada-agent
in pull mode cluster, replaced with the use ofkarmada register
.The benefits of doing this include:
karmadactl register
has more fine-grained RBAC permission control.karmadactl register
.Which issue(s) this PR fixes:
Parts of #5916
Special notes for your reviewer:
Does this PR introduce a user-facing change?: