-
Notifications
You must be signed in to change notification settings - Fork 54
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
Add route to get member cluster node #146
Conversation
Welcome @Heylosky! It looks like this is your first PR to karmada-io/dashboard 🎉 |
Signed-off-by: Heylosky <2547226479@qq.com>
6f3ccde
to
eb985e6
Compare
Hi @Heylosky Thanks for spotting and doing this. |
OK. |
e6af8c4
to
866c7ea
Compare
Signed-off-by: Heylosky <2547226479@qq.com>
866c7ea
to
6135bb1
Compare
Signed-off-by: Heylosky <2547226479@qq.com>
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: warjiang 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 |
@@ -233,6 +254,43 @@ func InClusterClientForKarmadaApiServer() kubeclient.Interface { | |||
return inClusterClientForKarmadaApiServer | |||
} | |||
|
|||
func InClusterClientForMemberCluster(clusterName string) kubeclient.Interface { |
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.
good 👍
What type of PR is this?
/kind feature
What this PR does / why we need it:
Currently our company is using karmada as a company-level cluster management platform. We plan to display more information on the dashboard and add some new features, such as the ability to display member-cluster-node information. This PR adds the ability to obtain member-cluster-node information through the karmada-dashboard-api component, in preparation for adding a UI page.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
In our usage scenario, the member cluster is isolated from the main cluster. We hope to display more information about the member cluster through the dashboard, such as deployment, pod, namespace, etc., not just the resources deployed by karmada. Please consider whether it can be added to future plans.
Does this PR introduce a user-facing change?: