-
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
Fix karmadactl addon
failed to install karmada-scheduler-estimator due to unknown flag
#5523
Conversation
Signed-off-by: chaosi-zju <[email protected]>
/cc @zhzhuang-zju |
/assign |
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 #5523 +/- ##
==========================================
- Coverage 32.45% 32.44% -0.01%
==========================================
Files 643 643
Lines 44497 44497
==========================================
- Hits 14440 14438 -2
- Misses 28962 28963 +1
- Partials 1095 1096 +1
Flags with carried forward coverage won't be shown. Click here to find out more. ☔ View full report in Codecov by Sentry. |
test report: $ kubectl get pods -o wide -n karmada-system
NAME READY STATUS RESTARTS AGE IP NODE NOMINATED NODE READINESS GATES
etcd-0 1/1 Running 0 10m 10.187.0.5 karmada-karmadactl-host-control-plane <none> <none>
karmada-aggregated-apiserver-7db6f685c6-kwr4z 1/1 Running 0 10m 10.187.0.7 karmada-karmadactl-host-control-plane <none> <none>
karmada-apiserver-799cfbb68f-df99k 1/1 Running 0 10m 10.187.0.6 karmada-karmadactl-host-control-plane <none> <none>
karmada-controller-manager-ffc79cbf5-829dn 1/1 Running 0 8m48s 10.187.0.10 karmada-karmadactl-host-control-plane <none> <none>
karmada-descheduler-744f98cb8f-9jz8c 1/1 Running 0 5m8s 10.187.0.13 karmada-karmadactl-host-control-plane <none> <none>
karmada-metrics-adapter-59cdb58586-w87xj 1/1 Running 0 4m20s 10.187.0.14 karmada-karmadactl-host-control-plane <none> <none>
karmada-scheduler-dbb6847f7-b64qv 1/1 Running 0 9m17s 10.187.0.9 karmada-karmadactl-host-control-plane <none> <none>
karmada-scheduler-estimator-member4-5896d89644-gprzw 1/1 Running 0 3m5s 10.187.0.15 karmada-karmadactl-host-control-plane <none> <none>
karmada-search-6c4f64c474-kf4c7 1/1 Running 0 6m7s 10.187.0.12 karmada-karmadactl-host-control-plane <none> <none>
karmada-webhook-666d8d6754-qx2fx 1/1 Running 0 8m11s 10.187.0.11 karmada-karmadactl-host-control-plane <none> <none>
kube-controller-manager-787569d669-fmhnv 1/1 Running 0 9m19s 10.187.0.8 karmada-karmadactl-host-control-plane <none> <none> |
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.
/retitle Fix karmadactl addon
failed to install karmada-scheduler-estimator due to unknown flag
karmadactl addon
failed to install karmada-scheduler-estimator due to unknown flag
This issue was introduced by #5040 ? mistakenly introduced not exist flag? |
Looks like it is The |
@chaosi-zju Thank you for correcting my previous mistake.
Yes, it seems that not all relevant parts were updated after the plan change. I will check to see if there are any remaining areas where this flag needs to be removed. |
/lgtm |
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
[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 |
…23-upstream-release-1.11 Automated cherry pick of #5523: Fix `karmadactl addon` failed to install karmada-scheduler-estimator due to unknown flag
What type of PR is this?
/kind bug
/kind cleanup
What this PR does / why we need it:
fix launch arguments when install estimator by karmadactl which caused its installation failure
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?: