[HsiuChuanHsu]

What type of PR is this?

/kind cleanup

What this PR does / why we need it?

Generate the KueueViz shared Ingress configuration from the configuration directory. Keep the generated configuration usable for installations outside Helm.

Fixes #15669

Useful notes for your reviewer

Release note

KueueViz: Added a generated Ingress manifest for non-Helm installations that serves the dashboard and backend from a single host, routing `/ws`, `/api`, and `/auth` to the backend and `/` to the frontend.

AI summary

Adds a generated single-host KueueViz manifest for non-Helm installations. The manifest routes /ws, /api, and /auth to the backend and / to the frontend. Helm generation now uses the shared Ingress configuration. Documentation includes host, TLS, and migration instructions.

Suggested release note

KueueViz: Added a single-host manifest that serves the dashboard and backend through one path-routed Ingress.

[netlify]

✅ Deploy Preview for kubernetes-sigs-kueue canceled.

Name	Link
🔨 Latest commit	3058826
🔍 Latest deploy log	https://app.netlify.com/projects/kubernetes-sigs-kueue/deploys/6ab06eb7721c6d0008193c48

[kubernetes-prow]

Hi @HsiuChuanHsu. 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 /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work.

Tip

We noticed you've done this a few times! Consider joining the org to skip this step and gain /lgtm and other bot rights. We recommend asking approvers on your previous PRs to sponsor you.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Details

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.

[coderabbitai]

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Repository: kubernetes-sigs/kueue/.coderabbit.yaml

Review profile: CHILL

Plan: Advanced

Run ID: b65e0124-14a8-442c-b654-463364c7e7c6

📥 Commits

Reviewing files that changed from the base of the PR and between 62bfb56 and 3058826.

📒 Files selected for processing (1)

• config/components/kueueviz/kustomization.yaml

Included review availability: Your plan provides up to 8 included reviews per hour; 7 remain after this review.

---

📝 Walkthrough

Walkthrough

The PR adds a single-host KueueViz Kustomize manifest with path-based routing. It adds Helm processing for the shared Ingress, preserves separate-host overlays, generates the manifest as an artifact, and updates deployment documentation.

Changes

KueueViz single-host deployment

Layer / File(s)	Summary
Single-host manifest and routing config/components/kueueviz/..., config/kueueviz-single-host/...	Adds one Ingress that routes /ws, /api, and /auth to the backend and / to the frontend. The overlay removes the separate component Ingresses and clears frontend backend URLs.
Helm ingress processing charts/kueue/templates/kueueviz/ingress.yaml, hack/processing-plan.yaml	Regenerates the Helm Ingress template and adds configurable host, ingress class, TLS, annotations, and conditional rendering for the shared Ingress.
Separate-host overlay compatibility config/kueueviz/kustomization.yaml, config/kueueviz/remove_shared_ingress.yaml	Removes the shared Ingress from the existing separate-host overlay.
Artifact and deployment documentation Makefile, site/content/en/docs/tasks/manage/enable_kueueviz.md	Builds kueueviz-single-host.yaml and documents installation, host and TLS changes, migration, and the rewrite-target warning.

Priority: ⬇️ Low

Estimated code review effort: 3 (Moderate) | ~25 minutes

Change: Feature

Suggested reviewers: mbobrovskyi

Sequence Diagram(s)

sequenceDiagram
  participant Browser
  participant KueueVizIngress
  participant KueueVizBackend
  participant KueueVizFrontend
  Browser->>KueueVizIngress: Request /ws, /api, or /auth
  KueueVizIngress->>KueueVizBackend: Route request to port 8080
  Browser->>KueueVizIngress: Request /
  KueueVizIngress->>KueueVizFrontend: Route request to port 8080
  KueueVizFrontend-->>Browser: Use the serving origin for WebSocket configuration

Loading

🚥 Pre-merge checks | ✅ 5

✅ Passed checks (5 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title clearly and concisely describes the primary change: generating a shared KueueViz Ingress from configuration.
Linked Issues check	✅ Passed	The PR meets the coding requirements in issue #15669. config/components/kueueviz/ingress.yaml defines kueueviz-ingress with /ws, /api, and /auth routed to kueueviz-backend:8080, and / ro…
Out of Scope Changes check	✅ Passed	The changes stay within issue #15669. The single-host overlay, deletion patches for the separate Ingress objects, frontend environment patch, Makefile artifact entry, documentation update, and removal…
Docstring Coverage	✅ Passed	No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check. Docstring coverage is scoped to functions touched by this diff. Analyzed 0 functions across 0…

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create a new PR

---

_{Comment @coderabbitai help to get the list of available commands.}

[tenzen-y]

/ok-to-test

[tenzen-y]

Thank you!
/lgtm
/approve

[kubernetes-prow]

LGTM label has been added.

Details

Git tree hash: 7926a464174f254a77f5997a4c5435fb9e6971fa

[kubernetes-prow]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: HsiuChuanHsu, tenzen-y

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [tenzen-y]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[tenzen-y]

IIUC, this is just automation and brings the Helm ingress to the config.

[tenzen-y]

/release-note-edit

KueueViz: Support a single comprehensive Ingress usage for non-Helm installations.

[HsiuChuanHsu]

IIUC, this is just automation and brings the Helm ingress to the config.

Yes. Thanks for the review.

[mbobrovskyi]

/release-note-edit

KueueViz: Added a generated Ingress manifest for non-Helm installations that serves the dashboard and backend from a single host, routing `/ws`, `/api`, and `/auth` to the backend and `/` to the frontend.