Skip to content

Fix kubeflow install doc#109

Merged
typhoonzero merged 3 commits intomasterfrom
fix_kubeflow_docs
Feb 26, 2026
Merged

Fix kubeflow install doc#109
typhoonzero merged 3 commits intomasterfrom
fix_kubeflow_docs

Conversation

@typhoonzero
Copy link
Contributor

@typhoonzero typhoonzero commented Feb 26, 2026

Summary by CodeRabbit

  • Documentation
    • Scoped oauth2-proxy certificate retrieval to the Global cluster context.
    • Replaced ConfigMap redirectURI flow with Platform Parameters under Platform Access URLs and added a clear example format.
    • Reworded post-deployment navigation from AML Advanced to Tools in Alauda AI.
    • Updated Profile deployment note to reference Alauda AI terminology.
    • Added YAML example for ServiceAccount and RoleBindings to support namespace binding.
    • Standardized plugin name to “Alauda Build of LeaderWorkerSet”.

@coderabbitai
Copy link

coderabbitai bot commented Feb 26, 2026

Walkthrough

This PR updates the Kubeflow installation docs: replaces the prior ConfigMap-based redirectURIs flow with a Platform Parameters (Platform Access URLs) flow, scopes oauth2-proxy certificate retrieval to the Global cluster, provides an explicit redirectURIs example (host/port with 30443), adjusts post-deployment navigation wording to Tools in Alauda AI, adds a YAML fragment for ServiceAccount/RoleBinding for namespace binding, and renames LWS plugin references to "Alauda Build of LeaderWorkerSet".

Changes

Cohort / File(s) Summary
Documentation
docs/en/installation/kubeflow.mdx
Replaced ConfigMap redirectURIs flow with Platform Parameters (Platform Access URLs) and added example; limited oauth2-proxy certificate retrieval to Global cluster; changed post-deployment navigation wording to Tools in Alauda AI; added YAML fragment for ServiceAccount default-editor and RoleBindings for namespace binding; renamed LWS plugin to "Alauda Build of LeaderWorkerSet"; minor wording/terminology updates throughout.

Estimated code review effort

🎯 2 (Simple) | ⏱️ ~10 minutes

Possibly related PRs

  • Add kubeflow deploy doc #95: Edits the same docs/en/installation/kubeflow.mdx around oauth2-proxy/dex redirect configuration and RoleBinding examples.

Poem

🐇 I hopped through docs with tiny paws,

Swapped ConfigMaps for Platform laws,
Redirects set and certs aligned,
Tools now show the path to find,
"Alauda Build" — a ribbon on our lines. 🎀

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Title check ❓ Inconclusive The title 'Fix kubeflow install doc' is vague and generic, using the non-descriptive term 'Fix' without specifying what was fixed or what the actual changes are. Use a more specific title that describes the actual changes, such as 'Update Kubeflow installation docs for Alauda AI terminology and oauth2-proxy configuration' to clarify the purpose of the updates.
✅ 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 fix_kubeflow_docs

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.

Copy link

@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.

🧹 Nitpick comments (2)
docs/en/installation/kubeflow.mdx (2)

106-107: Use a neutral placeholder instead of a concrete IP in the redirect URI example.

Line 107 currently shows a specific IP/port that can be copy-pasted accidentally and cause misconfiguration.

Suggested doc tweak
-      - https://192.168.139.133:30443/*
+      - https://<oidc_redirect_host>:<oidc_redirect_port>/*
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docs/en/installation/kubeflow.mdx` around lines 106 - 107, Replace the
concrete IP/port example "https://192.168.139.133:30443/*" with a neutral
placeholder to avoid accidental copy-paste; update the redirect URI example
referenced by oidcRedirectURL to something like "https://<HOST>:<PORT>/*" or
"https://your-domain.example/*" so readers must substitute their actual host and
port.

214-215: Polish note style for consistency.

Line 214 can be slightly tightened for documentation style consistency (sentence case and direct wording).

Suggested wording
-> Note: make sure to install LWS (Alauda Build of LeaderWorkerSet) plugin before deploying
+> Note: Make sure to install the LWS (Alauda Build of LeaderWorkerSet) plugin before deploying
🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docs/en/installation/kubeflow.mdx` around lines 214 - 215, Replace the
existing note line that reads "Note: make sure to install LWS (Alauda Build of
LeaderWorkerSet) plugin before deploying kubeflow-trainer, as LWS is a
dependency of kubeflow-trainer." with a tighter, sentence-case phrasing for
consistency; update the wording to something like "Note: install LWS (Alauda
Build of LeaderWorkerSet) before deploying kubeflow-trainer, as it is a
dependency." to use sentence case, remove redundancy, and keep the meaning
intact.
🤖 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/installation/kubeflow.mdx`:
- Around line 106-107: Replace the concrete IP/port example
"https://192.168.139.133:30443/*" with a neutral placeholder to avoid accidental
copy-paste; update the redirect URI example referenced by oidcRedirectURL to
something like "https://<HOST>:<PORT>/*" or "https://your-domain.example/*" so
readers must substitute their actual host and port.
- Around line 214-215: Replace the existing note line that reads "Note: make
sure to install LWS (Alauda Build of LeaderWorkerSet) plugin before deploying
kubeflow-trainer, as LWS is a dependency of kubeflow-trainer." with a tighter,
sentence-case phrasing for consistency; update the wording to something like
"Note: install LWS (Alauda Build of LeaderWorkerSet) before deploying
kubeflow-trainer, as it is a dependency." to use sentence case, remove
redundancy, and keep the meaning intact.

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 498a273 and 10c6c8c.

📒 Files selected for processing (1)
  • docs/en/installation/kubeflow.mdx

@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Feb 26, 2026

Deploying alauda-ai with  Cloudflare Pages  Cloudflare Pages

Latest commit: ad6378a
Status: ✅  Deploy successful!
Preview URL: https://07bd896c.alauda-ai.pages.dev
Branch Preview URL: https://fix-kubeflow-docs.alauda-ai.pages.dev

View logs

Copy link

@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.

Caution

Some comments are outside the diff and can’t be posted inline due to platform limitations.

⚠️ Outside diff range comments (1)
docs/en/installation/kubeflow.mdx (1)

22-27: ⚠️ Potential issue | 🟡 Minor

Clarify the required kubectl cluster context before fetching the cert

Line 22 says this is for the Global cluster, but Line 25 can still run against whatever context is currently active. Please explicitly instruct switching to the Global cluster first to avoid pulling the wrong dex.tls secret.

Suggested doc tweak
-Obtain the platform dex CA certificate for later use in **Global** cluster:
+Switch `kubectl` to the **Global** cluster, then obtain the platform dex CA certificate for later use:

 ```bash
+kubectl config use-context <global-cluster-context>
 crt=$(kubectl get secret -n cpaas-system dex.tls -o jsonpath='{.data.tls\.crt}')
 echo -n $crt | base64 -d
</details>

<details>
<summary>🤖 Prompt for AI Agents</summary>

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

In @docs/en/installation/kubeflow.mdx around lines 22 - 27, Clarify that the
kubectl commands must run against the Global cluster by adding an explicit step
to switch context before fetching the dex.tls secret: instruct the reader to run
kubectl config use-context (replace placeholder with
their Global cluster context) prior to the kubectl get secret -n cpaas-system
dex.tls ... and base64 decode steps so the dex.tls secret is retrieved from the
intended Global cluster context.


</details>

</blockquote></details>

</blockquote></details>
🤖 Prompt for all review comments with AI agents
Verify each finding against the current code and only fix it if needed.

Outside diff comments:
In `@docs/en/installation/kubeflow.mdx`:
- Around line 22-27: Clarify that the kubectl commands must run against the
Global cluster by adding an explicit step to switch context before fetching the
dex.tls secret: instruct the reader to run kubectl config use-context
<global-cluster-context> (replace placeholder with their Global cluster context)
prior to the kubectl get secret -n cpaas-system dex.tls ... and base64 decode
steps so the dex.tls secret is retrieved from the intended Global cluster
context.

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 10c6c8c and 0bac03f.

📒 Files selected for processing (1)
  • docs/en/installation/kubeflow.mdx

Copy link

@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.

🧹 Nitpick comments (1)
docs/en/installation/kubeflow.mdx (1)

126-145: YAML syntax and structure are correct.

The new ServiceAccount and RoleBinding resources are properly formatted. Minor observation: this code block (and the one at line 110) uses plain triple backticks while the YAML block at line 33 uses ```yaml. Consider adding the yaml language identifier for syntax highlighting consistency.

,

🤖 Prompt for AI Agents
Verify each finding against the current code and only fix it if needed.

In `@docs/en/installation/kubeflow.mdx` around lines 126 - 145, The Markdown code
fences for the Kubernetes resources (the ServiceAccount named "default-editor"
and the RoleBinding referencing ClusterRole "kubeflow-edit" in namespace
"kubeflow-admin-cpaas-io") need the YAML language identifier for consistent
syntax highlighting; locate the triple-backtick fences that wrap the block
containing the ServiceAccount/RoleBinding (and the similar block near the
earlier example) and change ``` to ```yaml so the fenced blocks explicitly
specify the yaml language.
🤖 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/installation/kubeflow.mdx`:
- Around line 126-145: The Markdown code fences for the Kubernetes resources
(the ServiceAccount named "default-editor" and the RoleBinding referencing
ClusterRole "kubeflow-edit" in namespace "kubeflow-admin-cpaas-io") need the
YAML language identifier for consistent syntax highlighting; locate the
triple-backtick fences that wrap the block containing the
ServiceAccount/RoleBinding (and the similar block near the earlier example) and
change ``` to ```yaml so the fenced blocks explicitly specify the yaml language.

ℹ️ Review info

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 0bac03f and ad6378a.

📒 Files selected for processing (1)
  • docs/en/installation/kubeflow.mdx

@liuwei-2622
Copy link

/test-pass

@typhoonzero typhoonzero merged commit 02e4dfc into master Feb 26, 2026
3 checks passed
@typhoonzero typhoonzero deleted the fix_kubeflow_docs branch February 26, 2026 09:40
typhoonzero added a commit that referenced this pull request Feb 26, 2026
* fix kubeflow install doc

* update

* update
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