Skip to content

Add kueue gap #165

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
luohua13 wants to merge 3 commits into
base: add-kuberay
Choose a base branch
from
+641 −4
Open

Add kueue gap #165

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
1952f7c
Add managing Alauda AI docs
luohua13 Mar 25, 2026
24ac7cf
update
luohua13 Mar 25, 2026
e9cf92f
replace project by namespace
luohua13 Mar 25, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
1 change: 1 addition & 0 deletions .gitignore
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -13,3 +13,4 @@

.claude
CLAUDE.md
.vscode/extensions.json
6 changes: 3 additions & 3 deletions docs/en/distributed_workloads/running-ray-based-distributed-workloads.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -20,7 +20,7 @@ The demo Jupyter notebooks from the CodeFlare SDK provide guidelines on how to u

#### Prerequisites

- You can access a data science cluster that is configured to run distributed workloads as described in [Managing distributed workloads](../kueue/how_to/config_quotas.mdx).
- You can access a data science cluster that is configured to run distributed workloads as described in [Managing distributed workloads](../managing/managing-distributed-workloads.mdx).
- You can access a namespace in Alauda AI, create a workbench, and run a default workbench image that contains the CodeFlare SDK, for example, the **Standard Data Science** notebook. For information about creating workbenches, see [Create Workbench](../workbench/how_to/create_workbench.mdx).
- You have logged in to Alauda AI, started your workbench, and logged in to JupyterLab.

Expand Down Expand Up @@ -64,7 +64,7 @@ In the examples in this procedure, you edit the demo Jupyter notebooks in Jupyte

#### Prerequisites

- You can access a data science cluster that is configured to run distributed workloads as described in [Managing distributed workloads](../kueue/how_to/config_quotas.mdx).
- You can access a data science cluster that is configured to run distributed workloads as described in [Managing distributed workloads](../managing/managing-distributed-workloads.mdx).
- You have installed the `Alauda Build of KubeRay Operator` cluster plugin in your data science cluster, see [Install Alauda Build of KubeRay Operator](../kuberay/install.mdx).
- You can access the following software from your data science cluster:
- A Ray cluster image that is compatible with your hardware architecture
Expand Down Expand Up @@ -175,7 +175,7 @@ The `3_widget_example.ipynb` demo Jupyter notebook shows all of the available in

#### Prerequisites

- You can access a data science cluster that is configured to run distributed workloads as described in [Managing distributed workloads](../kueue/how_to/config_quotas.mdx).
- You can access a data science cluster that is configured to run distributed workloads as described in [Managing distributed workloads](../managing/managing-distributed-workloads.mdx).
- You have installed the `Alauda Build of KubeRay Operator` cluster plugin in your data science cluster, see [Install Alauda Build of KubeRay Operator](../kuberay/install.mdx).
- You can access the following software from your data science cluster:
- A Ray cluster image that is compatible with your hardware architecture
Expand Down
2 changes: 1 addition & 1 deletion docs/en/distributed_workloads/troubleshooting.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -72,7 +72,7 @@ After you run the `cluster.apply()` command, the following error is shown:
```
ApiException: (500)
Reason: Internal Server Error
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Internal error occurred: failed calling webhook \"mraycluster.kb.io\": failed to call webhook: Post \"https://kueue-webhook-service.redhat-ods-applications.svc:443/mutate-ray-io-v1-raycluster?timeout=10s\": no endpoints available for service \"kueue-webhook-service\"","reason":"InternalError","details":{"causes":[{"message":"failed calling webhook \"mraycluster.kb.io\": failed to call webhook: Post \"https://kueue-webhook-service.redhat-ods-applications.svc:443/mutate-ray-io-v1-raycluster?timeout=10s\": no endpoints available for service \"kueue-webhook-service\""}]},"code":500}
HTTP response body: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"Internal error occurred: failed calling webhook \"mraycluster.kb.io\": failed to call webhook: Post \"https://kueue-webhook-service.cpaas-system.svc:443/mutate-ray-io-v1-raycluster?timeout=10s\": no endpoints available for service \"kueue-webhook-service\"","reason":"InternalError","details":{"causes":[{"message":"failed calling webhook \"mraycluster.kb.io\": failed to call webhook: Post \"https://kueue-webhook-service.cpaas-system.svc:443/mutate-ray-io-v1-raycluster?timeout=10s\": no endpoints available for service \"kueue-webhook-service\""}]},"code":500}
```

### Diagnosis
Expand Down
9 changes: 9 additions & 0 deletions docs/en/managing/index.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,9 @@
---
weight: 75
---

# Managing Alauda AI

As an Alauda Container Platform cluster administrator, you can manage Alauda AI users and groups, the dashboard interface and applications, deployment resources, accelerators, distributed workloads, and data backup.

<Overview />
Loading