Upgrade ai 1.5 to 2.0

[fyuan1316]

Summary by CodeRabbit

• Documentation
  • Updated upgrade guide with version information for 1.5 and 2.0 releases.
  • Added Pre-Upgrade Operations section with required steps for stopping services.
  • Added Post-Upgrade Operations section with required steps for updating services.
  • Added mandatory pre-upgrade warning for the upgrade process.

[coderabbitai]

Walkthrough

Documentation update to the upgrade guide adding Pre-Upgrade and Post-Upgrade operation sections. Version constants bumped from 1.4/1.5 to 1.5/2.0. New sections detail stopping InferenceServices before upgrade and updating them post-upgrade, with step-by-step YAML and CLI examples provided.

Changes

Cohort / File(s)	Summary
Upgrade Guide Documentation docs/en/upgrade/upgrade-from-previous-version.mdx	Version number updates from 1.4/1.5 to 1.5/2.0. New Pre-Upgrade Operations section with KServe stop annotation instructions and YAML/CLI examples. New Post-Upgrade Operations section detailing InferenceServices updates with step-by-step guidance and examples.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

• chore: add upgrade workbench AI-23623 #94: Modifies the same upgrade documentation file and updates version constants.
• AI-None improve 1.4 install #26: Updates upgrade documentation with InferenceServices migration and stopping guidance steps.
• fix upgrade version and prepare #80: Extends the same upgrade documentation with pre/post-upgrade procedures.

Poem

🐰 Hop, hop! The upgrade guide now stands tall,
With pre and post steps for one and for all,
Stop your services, then update with care,
From 1.5 to 2.0 — a journey so fair!

🚥 Pre-merge checks | ✅ 3

✅ Passed checks (3 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.
Title check	✅ Passed	The title directly reflects the main change: updating documentation to document the upgrade path from version 1.5 to 2.0, matching the version bumps and upgrade instructions added.
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 upgrade-ai-1.5-to-2.0

---

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

• X
• Mastodon
• Reddit
• LinkedIn

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

[coderabbitai]

🧹 Nitpick comments (1)

docs/en/upgrade/upgrade-from-previous-version.mdx (1)

36-40: Clarify how to identify stopped inference services.

The instruction tells users to list all inference services, but doesn't explain how to determine which ones are in a "stopped" state from the command output. Users need to know what field, status, or condition to look for.

Consider adding guidance such as filtering by a specific status column or label, for example:

 1. List all inference services that are currently stopped:

    ```bash
    kubectl get inferenceservices --all-namespaces
    ```
+
+   Look for services where the `READY` column shows `False` and replicas are scaled to zero, or check for services that were previously stopped via your platform's UI.

🤖 Prompt for AI Agents

Verify each finding against the current code and only fix it if needed.

In `@docs/en/upgrade/upgrade-from-previous-version.mdx` around lines 36 - 40, The
docs step shows how to list inference services but doesn't explain how to spot
"stopped" services; update the text near the `kubectl get inferenceservices
--all-namespaces` example to tell users which fields to inspect (e.g., check the
READY column for `False`, check the REPLICAS column for `0`, and/or examine
STATUS or conditions for `ScaledDown`/`NotReady`), and add an alternative
suggestion to run `kubectl describe inferenceservice <name>` or filter by
status/label if they need more detail.

🤖 Prompt for all review comments with AI agents

Verify each finding against the current code and only fix it if needed.

Nitpick comments:
In `@docs/en/upgrade/upgrade-from-previous-version.mdx`:
- Around line 36-40: The docs step shows how to list inference services but
doesn't explain how to spot "stopped" services; update the text near the
`kubectl get inferenceservices --all-namespaces` example to tell users which
fields to inspect (e.g., check the READY column for `False`, check the REPLICAS
column for `0`, and/or examine STATUS or conditions for
`ScaledDown`/`NotReady`), and add an alternative suggestion to run `kubectl
describe inferenceservice <name>` or filter by status/label if they need more
detail.

---

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 02e4dfc and 9603277.

📒 Files selected for processing (1)

• docs/en/upgrade/upgrade-from-previous-version.mdx

[cloudflare-workers-and-pages]

Deploying alauda-ai with    Cloudflare Pages

Latest commit:	9603277
Status:	✅  Deploy successful!
Preview URL:	https://b1702f57.alauda-ai.pages.dev
Branch Preview URL:	https://upgrade-ai-1-5-to-2-0.alauda-ai.pages.dev

View logs