docs: add Open Cluster Management ClusterProfile link#9018
Conversation
Signed-off-by: Qing Hao <qhao@redhat.com>
k8s-ci-robot
added
kind/documentation
✅ Deploy Preview for kubernetes-sigs-kueue ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
k8s-ci-robot
added
the
cncf-cla: yes
k8s-ci-robot
added
the
needs-ok-to-test
|
Hi @haoqing0110. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
k8s-ci-robot
added
the
size/XS
|
/ok-to-test |
k8s-ci-robot
added
ok-to-test
|
/release-note-edit |
k8s-ci-robot
added
release-note-none
|
|
||
| {{% /alert %}} | ||
|
|
||
| #### Cluster management platform inventory |
There was a problem hiding this comment.
cc @mimowo
This "setup_multikueue" page is getting quite long.
Should we consider moving things like ClusterProfile to our main MultiKueue page?
It seems that Cluster Inventory / ClusterProfile is an important topic and its making this "task" page grow.
I also see that we provide examples for GCP in some areas and in this page we are linking to OCM docs as a full setup for clusterprofile. I think this is fine but maybe we could just add a section linking to providers and we can have a clear place to go to set this up.
There was a problem hiding this comment.
cc @kshalot @olekzabl who are now leading the MultiKueue effort on our side.
Should we consider moving things like ClusterProfile to our main MultiKueue page?
Yes, I think we should re-organize, so that users who land here are not scared "oh gosh, why is that so long, it must be super complex". Ideally the landing page can fully fit on the screen.
One way to achieve that on a Kind cluster, and I think super easy is to use E2E_MODE=dev make kind-image-build test-multikueue-e2e, and voila :)
Then we could have subpage about production setup, and subpage about using ClusterProfile.
I also see that we provide examples for GCP in some areas and in this page we are linking to OCM docs as a full setup for clusterprofile.
👍 I would like to put these in some section at the bottom like "Other resources", and provide links to cloud-provider speciific content.
There was a problem hiding this comment.
Still, I don't think this is an issue specific to this particular PR, more of the follow up probably, let me open an issue: #9032
|
@mimowo: once the present PR merges, I will cherry-pick it on top of DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: haoqing0110, mimowo The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
k8s-ci-robot
added
the
approved
|
Yea! my comment is more of a general cleanup. /lgtm Thank you @haoqing0110! |
k8s-ci-robot
added
the
lgtm
|
LGTM label has been added. DetailsGit tree hash: b0d8ebd90cff6aa818c07c571b23703ca5c16276 |
|
@mimowo: new pull request created: #9035 DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
7 participants
What type of PR is this?
/kind documentation
What this PR does / why we need it:
Open Cluster Management has an integration with MultiKueue, and it now supports ClusterProfile.
Update the doc to include the link.
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer:
Does this PR introduce a user-facing change?