Skip to content

Rls 1.5/fix upgrade version#92

Merged
fyuan1316 merged 4 commits intorelease-1.5from
rls-1.5/fix-upgrade-version
Feb 3, 2026
Merged

Rls 1.5/fix upgrade version#92
fyuan1316 merged 4 commits intorelease-1.5from
rls-1.5/fix-upgrade-version

Conversation

@fyuan1316
Copy link
Copy Markdown
Contributor

@fyuan1316 fyuan1316 commented Feb 2, 2026

Summary by CodeRabbit

  • Documentation
    • Removed several legacy install/upgrade and workspace-kind guides.
    • Added a full 1.4→1.5 upgrade guide with verification steps.
    • Introduced Fine‑tuning and Pre‑training docs (overview, how‑tos, templates, task/workflow guidance).
    • Added Alauda Build of Kueue docs (install, how‑tos, quotas, scheduling, RBAC, Tekton integration).
    • New monitoring, tools menu, installation, model‑runtime examples, and updated release notes and site version references.

@coderabbitai
Copy link
Copy Markdown

coderabbitai bot commented Feb 2, 2026

Caution

Review failed

Failed to post review comments

Walkthrough

Removes the old AI 1.3→1.4 upgrade guide and adds a new upgrade guide for 1.4→1.5; concurrently adds and updates many documentation pages across fine‑tuning, pre‑training, kueue, installation, monitoring, model inference, workbench, and public workspace manifests, plus site/version bumps and config tweaks.

Changes

Cohort / File(s) Summary
Upgrade guides
docs/en/upgrade/upgrade-from-ai-1.3.mdx, docs/en/upgrade/upgrade-from-previous-version.mdx
Deleted the AI 1.3→1.4 upgrade doc and added a new 1.4→1.5 upgrade guide (install/upgrade steps, verification, prev/cur version vars).
Fine‑tuning & pre‑training
docs/en/fine_tuning/..., docs/en/pre-training/...
Added multiple fine‑tuning pages (intro, how‑to, templates, create tasks) and parallel pre‑training docs linking into fine‑tuning content.
Kueue (Alauda Build)
docs/en/kueue/...
Added comprehensive Kueue docs: intro, install, many how‑tos (config quotas, fair sharing, gang scheduling, tekton, RBAC, cohorts, monitoring pending workloads).
Installation & plugins
docs/en/installation/..., docs/en/installation/smart-doc.mdx (deleted)
Added tooling and fine‑tuning installation pages, small ai-cluster FAQ/formatting edits; removed smart-doc (Hyperflux) doc.
Workbench & WorkspaceKind manifests
docs/en/workbench/..., docs/public/workbench/codeserver_v1beta1_workspacekind.yaml, docs/public/workbench/jupyterlab_v1beta1_workspacekind.yaml
Updated workbench how‑to page; removed create_workspace_kind doc and deleted the public WorkspaceKind YAML manifests (codeserver, jupyterlab).
Model inference runtimes
docs/en/model_inference/inference_service/how_to/custom_inference_runtime.mdx
Reworked runtime doc: renamed sections, added MLServer and MindIE (Ascend NPU) examples, runtime comparison table and scheduler/security notes.
Monitoring & dashboards
docs/en/monitoring_ops/resource_monitoring/...
Added dashboard creation how‑to and troubleshooting doc for dashboard loading stuck scenario.
Release notes & overview
docs/en/overview/release_notes.mdx, docs/en/overview/architecture.mdx
Bumped release to 1.5.0 and substantially rewrote features/deprecations; updated architecture image path and minor formatting.
Public tools & menu config
docs/en/installation/tools.mdx
Added Tools Menu Configuration doc describing ConfigMap auto‑discovery, tags, and centraldashboard aggregation.
Site/config changes
sites.yaml, doom.config.yml
Bumped several site component versions and updated doom.jira queries for AI‑v1.5.0 release criteria.
Other docs scaffolding
assorted index/how‑to MDX files (monitoring, kueue, fine‑tuning, pre‑training)
Added multiple index/how‑to frontmatter pages rendering Overview components and small structural edits across docs.

Estimated code review effort

🎯 4 (Complex) | ⏱️ ~45 minutes

Possibly related PRs

Suggested reviewers

  • zhaomingkun1030
  • typhoonzero

Poem

🐰 I hopped through docs both old and new,
Brought guides and runtimes into view,
I burrowed out configs, pruned YAML leaves,
New upgrade paths and fine‑tune sheaves —
A tiny rabbit cheers the doc‑tree bloom! 🌿

🚥 Pre-merge checks | ✅ 2 | ❌ 1
❌ Failed checks (1 inconclusive)
Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'Rls 1.5/fix upgrade version' is vague and uses non-descriptive abbreviations; it does not clearly convey the primary changes in the pull request. Provide a more descriptive title that clearly summarizes the main changes, such as 'Add fine-tuning and pre-training documentation with version 1.5 updates' or similar.
✅ Passed checks (2 passed)
Check name Status Explanation
Description Check ✅ Passed Check skipped - CodeRabbit’s high-level summary is enabled.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.

✨ Finishing touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Post copyable unit tests in a comment
  • Commit unit tests in branch rls-1.5/fix-upgrade-version

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@liuwei-2622
Copy link
Copy Markdown

/test-pass

Copy link
Copy Markdown

@coderabbitai coderabbitai bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Actionable comments posted: 3

🤖 Fix all issues with AI agents
In `@docs/en/upgrade/upgrade-from-previous-version.mdx`:
- Around line 55-57: The admonition block using :::info contains extra leading
spaces that cause its inner text to render as a code block; locate the :::info
block (the line starting with ":::info") and left-align the inner sentence "Once
the new version is uploaded and recognized by the platform, an upgrade prompt
will appear at the top of the operator's page." so it has no extra indentation
relative to :::info, then ensure the block is properly closed with ::: on its
own line; also remove any leading backticks or fences inside that block if
present.
- Around line 62-73: The text has grammar errors and mismatched casing with the
sample output; update the sentence that references the AmlCluster resource and
the expected output to read: "Check the status field of the AmlCluster resource
named `default` by running `kubectl get amlcluster default`." Then adjust the
expectation sentence to match the sample output headers and values exactly, for
example: "The output should show READY and REASON columns, e.g. `default   True 
Succeeded`." Ensure you reference `AmlCluster`, the command `kubectl get
amlcluster default`, and the sample output headers `READY` and `REASON`.
- Around line 75-86: The text and sample output for the KnativeServing resource
named `default-knative-serving` disagree (text says `InstallSuccessful` while
sample shows `UpgradeSuccessful`) and the sentence has a grammar error; update
the descriptive sentence to match the sample output by replacing
`InstallSuccessful` with `UpgradeSuccessful` and fix the grammar to "Should
return `UpgradeSuccessful`" (refer to the `KnativeServing` example and the line
mentioning `default-knative-serving` to locate the change).

Comment on lines +55 to +57
:::info
Once the new version is uploaded and recognized by the platform, an upgrade prompt will appear at the top of the operator's page.
:::
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Fix admonition content indentation to avoid code-block rendering.

The extra indentation inside the :::info block likely renders as a code block in MDX.

✂️ Suggested formatting fix
 :::info
-    Once the new version is uploaded and recognized by the platform, an upgrade prompt will appear at the top of the operator's page.
+Once the new version is uploaded and recognized by the platform, an upgrade prompt will appear at the top of the operator's page.
 :::
📝 Committable suggestion

‼️ IMPORTANT
Carefully review the code before committing. Ensure that it accurately replaces the highlighted code, contains no missing lines, and has no issues with indentation. Thoroughly test & benchmark the code to ensure it meets the requirements.

Suggested change
:::info
Once the new version is uploaded and recognized by the platform, an upgrade prompt will appear at the top of the operator's page.
:::
:::info
Once the new version is uploaded and recognized by the platform, an upgrade prompt will appear at the top of the operator's page.
:::
🤖 Prompt for AI Agents
In `@docs/en/upgrade/upgrade-from-previous-version.mdx` around lines 55 - 57, The
admonition block using :::info contains extra leading spaces that cause its
inner text to render as a code block; locate the :::info block (the line
starting with ":::info") and left-align the inner sentence "Once the new version
is uploaded and recognized by the platform, an upgrade prompt will appear at the
top of the operator's page." so it has no extra indentation relative to :::info,
then ensure the block is properly closed with ::: on its own line; also remove
any leading backticks or fences inside that block if present.

Comment on lines +62 to +73
Check the status field from the `AmlCluster` resource which named `default`:

```bash
kubectl get amlcluster default
```

Should returns `Ready`:

```
NAME READY REASON
default True Succeeded
```
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Tighten grammar and align text with the sample output.

There are grammar issues (“which named”, “Should returns”) and the text says “Ready” while the sample shows READY/REASON.

✏️ Suggested wording
-Check the status field from the `AmlCluster` resource which named `default`:
+Check the status field of the `AmlCluster` resource named `default`:

-Should returns `Ready`:
+It should show `READY=True` and `REASON=Succeeded`:
🤖 Prompt for AI Agents
In `@docs/en/upgrade/upgrade-from-previous-version.mdx` around lines 62 - 73, The
text has grammar errors and mismatched casing with the sample output; update the
sentence that references the AmlCluster resource and the expected output to
read: "Check the status field of the AmlCluster resource named `default` by
running `kubectl get amlcluster default`." Then adjust the expectation sentence
to match the sample output headers and values exactly, for example: "The output
should show READY and REASON columns, e.g. `default   True    Succeeded`."
Ensure you reference `AmlCluster`, the command `kubectl get amlcluster default`,
and the sample output headers `READY` and `REASON`.

Comment on lines +75 to +86
Check the status field from the `KnativeServing` resource which named `default-knative-serving`:

```bash
kubectl get KnativeServing.components.aml.dev default-knative-serving
```

Should returns `InstallSuccessful`:

```
NAME DEPLOYED REASON
default-knative-serving True UpgradeSuccessful
```
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

⚠️ Potential issue | 🟡 Minor

Resolve mismatch between expected reason text and sample output.

The text says InstallSuccessful, but the sample output shows UpgradeSuccessful. Align one of them, and fix grammar.

✏️ Suggested wording (matching the sample)
-Check the status field from the `KnativeServing` resource which named `default-knative-serving`:
+Check the status field of the `KnativeServing` resource named `default-knative-serving`:

-Should returns `InstallSuccessful`:
+It should show `DEPLOYED=True` and `REASON=UpgradeSuccessful`:
🤖 Prompt for AI Agents
In `@docs/en/upgrade/upgrade-from-previous-version.mdx` around lines 75 - 86, The
text and sample output for the KnativeServing resource named
`default-knative-serving` disagree (text says `InstallSuccessful` while sample
shows `UpgradeSuccessful`) and the sentence has a grammar error; update the
descriptive sentence to match the sample output by replacing `InstallSuccessful`
with `UpgradeSuccessful` and fix the grammar to "Should return
`UpgradeSuccessful`" (refer to the `KnativeServing` example and the line
mentioning `default-knative-serving` to locate the change).

@cloudflare-workers-and-pages
Copy link
Copy Markdown

Deploying alauda-ai with  Cloudflare Pages  Cloudflare Pages

Latest commit: 4295296
Status: ✅  Deploy successful!
Preview URL: https://dc879c4b.alauda-ai.pages.dev
Branch Preview URL: https://rls-1-5-fix-upgrade-version.alauda-ai.pages.dev

View logs

@fyuan1316 fyuan1316 force-pushed the rls-1.5/fix-upgrade-version branch from 4295296 to e2a2274 Compare February 3, 2026 07:39
@fyuan1316 fyuan1316 changed the base branch from master to release-1.5 February 3, 2026 07:40
@fyuan1316 fyuan1316 merged commit 4f5973f into release-1.5 Feb 3, 2026
0 of 2 checks passed
@coderabbitai coderabbitai bot mentioned this pull request Mar 24, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants