Add Mylo AI assistant page for Calico Cloud#2619
Add Mylo AI assistant page for Calico Cloud#2619ctauchen wants to merge 5 commits intotigera:mainfrom
Conversation
✅ Deploy Preview for calico-docs-preview-next ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview succeeded!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
There was a problem hiding this comment.
Pull request overview
Adds Calico Cloud documentation for “Mylo”, an in-product AI assistant, and wires it into the Calico Cloud sidebar under Tutorials → Calico Cloud features.
Changes:
- Add new MDX doc page describing Mylo capabilities and example prompts.
- Add the new page to
sidebars-calico-cloud.jsso it appears in navigation.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
sidebars-calico-cloud.js |
Adds the new mylo-ai doc to the Calico Cloud features tutorial list. |
calico-cloud/tutorials/calico-cloud-features/mylo-ai.mdx |
Introduces a new Mylo feature overview page, including a data privacy/security section. |
| It helps you manage and secure your Kubernetes clusters by answering questions about workloads and network traffic, recommending network policies, and troubleshooting connectivity issues — all through natural language. | ||
|
|
||
| What sets Mylo apart from a general-purpose AI is that it has real-time, read-only access to your actual cluster environment. | ||
| Mylo can query your flow logs (including flow, DNS, and L7 logs), inspect Kubernetes resources (anything accessible via kubectl), and draw on a knowledge base built from Calico and Kubernetes documentation. |
There was a problem hiding this comment.
In this repo, command names are consistently formatted as inline code (for example, kubectl). Here kubectl is plain text, and the parenthetical is also a bit redundant/unclear (“flow logs (including flow, DNS, and L7 logs)”). Consider formatting kubectl as inline code and tightening the wording of the log types for readability and consistency.
| Mylo can query your flow logs (including flow, DNS, and L7 logs), inspect Kubernetes resources (anything accessible via kubectl), and draw on a knowledge base built from Calico and Kubernetes documentation. | |
| Mylo can query your flow, DNS, and L7 logs, inspect Kubernetes resources (anything accessible via `kubectl`), and draw on a knowledge base built from Calico and Kubernetes documentation. |
| Queries are processed using OpenAI through a Tigera enterprise account. | ||
| This is a contractual enterprise arrangement — not a consumer API. | ||
|
|
||
| **Does OpenAI train on my data?** | ||
|
|
||
| No. Your data is never used for model training or improvement. | ||
| The enterprise agreement explicitly prohibits this. | ||
|
|
||
| **Does OpenAI store my data?** | ||
|
|
||
| No. Data is not retained by OpenAI after processing your request. |
There was a problem hiding this comment.
The Data privacy and security section makes absolute, vendor-specific guarantees (OpenAI processing, no training, no retention). Since this repo doesn’t appear to reference an authoritative policy elsewhere, it would be safer to (a) link to an official Tigera/Calico Cloud privacy/security statement and/or (b) soften the wording to match what is contractually guaranteed and may change over time (provider, retention terms).
| Queries are processed using OpenAI through a Tigera enterprise account. | |
| This is a contractual enterprise arrangement — not a consumer API. | |
| **Does OpenAI train on my data?** | |
| No. Your data is never used for model training or improvement. | |
| The enterprise agreement explicitly prohibits this. | |
| **Does OpenAI store my data?** | |
| No. Data is not retained by OpenAI after processing your request. | |
| Yes. Mylo uses third-party AI services that Tigera operates on your behalf. | |
| Today, this includes providers such as OpenAI accessed through Tigera-managed enterprise accounts, not consumer APIs. | |
| **Does the AI provider train on my data?** | |
| The AI service providers used by Mylo are contractually restricted from using your data to train or improve their models for other customers. | |
| For the most current information about how Tigera handles customer data, see the [Tigera Privacy Policy](https://www.tigera.io/privacy-policy/). | |
| **Does the AI provider store my data?** | |
| The AI service providers used by Mylo may apply retention and logging policies that are governed by Tigera’s agreements with those providers and their own terms, which may change over time. | |
| For authoritative details on data handling and retention, refer to the [Tigera Privacy Policy](https://www.tigera.io/privacy-policy/). |
Adds a new documentation page covering Mylo, the AI-powered assistant in Calico Cloud, including use cases and data privacy details. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Adds an important callout directing users to contact Support to activate Mylo, plus an additional resources section with links to Support, flow logs, and network policy docs. Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
…pdates for Mylo Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
9368313 to
e478a0a
Compare
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Summary
Test plan
🤖 Generated with Claude Code