-
Notifications
You must be signed in to change notification settings - Fork 358
add blog on scaling Ayscale ray on AKS #5601
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.
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
base: master
Are you sure you want to change the base?
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
Adds a new AKS blog post that describes how to run/scale Ray workloads on AKS with Anyscale, covering multi-region capacity, unified storage (BlobFuse2), and service-principal-based authentication. It also includes diagram assets (SVGs) and their Mermaid sources to illustrate the storage and authentication flows.
Changes:
- Add new blog post content for “Scaling Ray on AKS” with examples and architecture guidance.
- Add Mermaid source diagrams for storage and authentication flows, plus exported SVG versions.
- Add supporting screenshots used by the post.
Reviewed changes
Copilot reviewed 3 out of 7 changed files in this pull request and generated 9 comments.
Show a summary per file
| File | Description |
|---|---|
| website/blog/2026-02-13-scaling-ray-aks/index.md | New blog post describing scaling Ray on AKS with multi-region, storage, and auth guidance |
| website/blog/2026-02-13-scaling-ray-aks/cluster-storage.mmd | Mermaid source for the cluster storage architecture diagram |
| website/blog/2026-02-13-scaling-ray-aks/cluster-storage.svg | Exported SVG for the cluster storage architecture diagram |
| website/blog/2026-02-13-scaling-ray-aks/auth-flow.mmd | Mermaid source for the service principal authentication flow diagram |
| website/blog/2026-02-13-scaling-ray-aks/auth-flow.svg | Exported SVG for the authentication flow diagram |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Pull request overview
Copilot reviewed 3 out of 7 changed files in this pull request and generated 2 comments.
| - anson-qian | ||
| - bob-mital | ||
| - kenneth-kilty | ||
| categories: |
Copilot
AI
Feb 12, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The frontmatter includes a categories: field with no value. This field is not used in other blog posts in the repository and appears to be unnecessary. According to the Docusaurus blog plugin, blog posts use tags for categorization, not a separate categories field. This empty field should be removed.
| categories: |
| - Fine-grained RBAC for Azure resource access | ||
| - Full audit trails through Azure Activity Logs | ||
|
|
||
| The following diagram illustrates how service principal enables the Anyscale Kubernetes Operator to authenticate without storing credentials: |
Copilot
AI
Feb 12, 2026
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
The sentence is missing an article before "service principal". It should be either "how a service principal enables" or "how the service principal enables". Based on the context describing a specific authentication flow, "the service principal" would be more appropriate.
| The following diagram illustrates how service principal enables the Anyscale Kubernetes Operator to authenticate without storing credentials: | |
| The following diagram illustrates how the service principal enables the Anyscale Kubernetes Operator to authenticate without storing credentials: |
No description provided.