Document KueueViz installation in a production suitable documentation

[akram]

What would you like to be cleaned:

Document KueueViz installation in a production suitable documentation

Why is this needed:

KueueViz is getting promoted form experimental to non-experimental and aims to reach production release.
For this to happen, users need a properly documentation installation process available on kueue website.

[akram]

/kind dashboard

[akram]

/kind documentation

[kafonek]

@akram if it helps, here's my experience deploying KueueViz:

Local (docker-desktop) deployment:

• kubectl port-forward svc/kueue-kueue-viz-frontend -n kueue-system 8080
• kubectl port-forward svc/kueue-kueue-viz-backend -n kueue-system 8081:8080
• Edit the kueue-viz-frontend Deployment to set env REACT_APP_WEBSOCKET_URL=ws://localhost:8081

For a multi-user cluster that controls ingress through Twingate-style software defined perimeter, the setup was roughly the same just switch out kubectl port-forward with defined uris. One small quality of life change would be defining the backend uri in the helm chart.

[akram]

@kafonek thank you for the feedback. This is also what I use for local testing. And I want to document the different cases like:

• vanilla kubernetes with ingress controller installed
• kubernetes without ingress controller
• optionally OpenShift

all these 3 scenarios works but requires a bit of guidance

[tenzen-y]

/remove-kind cleanup

[mimowo]

/help wanted
I think this could be a subpage under https://kueue.sigs.k8s.io/docs/tasks/manage/, say "Enable KueueViz".

cc @kannon92 @akram do you know some folks with cycles to prepare such a doc?

[mimowo]

/help-wanted

[mimowo]

/good-first-issue

[k8s-ci-robot]

@mimowo:
This request has been marked as suitable for new contributors.

Guidelines

Please ensure that the issue body includes answers to the following questions:

• Why are we solving this issue?
• To address this issue, are there any code changes? If there are code changes, what needs to be done in the code and what places can the assignee treat as reference points?
• How can the assignee reach out to you for help?

For more details on the requirements of such an issue, please see here and ensure that they are met.

If this request no longer meets these requirements, the label can be removed
by commenting with the /remove-good-first-issue command.

In response to this:

/good-first-issue

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.