Skip to content

Commit 47dc3ef

Browse files
committed
docs: add v1.0.0-rc.2 pre-release documentation version
Signed-off-by: Miraj Abeysekara <miraj@wso2.com>
1 parent e7e2d06 commit 47dc3ef

137 files changed

Lines changed: 32482 additions & 0 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

docusaurus.config.ts

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -84,6 +84,9 @@ const config: Config = {
8484
docs: {
8585
lastVersion: 'v0.17.x',
8686
versions: {
87+
'v1.0.0-rc.2': {
88+
label: 'v1.0.0-rc.2 (pre-release)',
89+
},
8790
'v1.0.0-rc.1': {
8891
label: 'v1.0.0-rc.1 (pre-release)',
8992
},
Lines changed: 13 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,13 @@
1+
[//] # (This file stores the constants used across the documentation.)
2+
3+
export const versions = {
4+
dockerTag: "v1.0.0-rc.2",
5+
githubRef: "release-v1.0.0-rc.2", // Used for the GitHub Raw URL references. Example: main, latest, v0.1.0
6+
helmChart: "1.0.0-rc.2",
7+
helmSource: "oci://ghcr.io/openchoreo/helm-charts",
8+
};
9+
10+
export const defaultCredentials = {
11+
username: "admin@openchoreo.dev",
12+
password: "Admin@123",
13+
};
Lines changed: 70 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,70 @@
1+
---
2+
title: MCP Prompt Scenarios
3+
---
4+
5+
# MCP Prompt Scenarios
6+
7+
This page provides a collection of practical prompt scenarios for using the OpenChoreo MCP server with AI assistants. Each scenario is a hands-on guide that walks you through real-world tasks using natural language prompts.
8+
9+
## Prerequisites
10+
11+
Before trying these scenarios:
12+
13+
1. **Configure your MCP server** — follow the [Configuring MCP Servers with AI Assistants](./mcp-servers.mdx) guide
14+
2. **Review available tools** — see the [MCP Servers Reference](../reference/mcp-servers.mdx) for the full list of MCP tools
15+
16+
## Scenarios
17+
18+
### 1. Getting Started
19+
20+
Learn the basics of connecting your AI assistant to OpenChoreo and performing simple operations like listing namespaces and projects.
21+
22+
**Time:** ~2 minutes
23+
24+
[View guide on GitHub →](https://github.com/openchoreo/openchoreo/tree/main/samples/mcp/getting-started)
25+
26+
---
27+
28+
### 2. Service Deployment
29+
30+
Deploy a complete service from source code to production using the OpenChoreo MCP server. Choose between a step-by-step guided walkthrough or a natural conversation-based deployment.
31+
32+
**Time:** ~15-20 minutes
33+
34+
[View guide on GitHub →](https://github.com/openchoreo/openchoreo/tree/main/samples/mcp/service-deployment)
35+
36+
---
37+
38+
### 3. Log Analysis & Debugging
39+
40+
Debug a cascading failure in the GCP Microservices Demo (Online Boutique) application. You'll intentionally break the product catalog service by scaling it to zero replicas, then use AI-assisted observability — logs, distributed traces, and deployment inspection — to diagnose and fix the issue across service boundaries.
41+
42+
**Key MCP tools:** `list_components`, `query_component_logs`, `query_traces`, `query_trace_spans`, `get_release_binding`, `update_release_binding`
43+
44+
**Time:** ~10 minutes
45+
46+
[View guide on GitHub →](https://github.com/openchoreo/openchoreo/tree/main/samples/mcp/log-analysis)
47+
48+
---
49+
50+
### 4. Build Failure Diagnosis
51+
52+
Debug a Docker build failure in the Go Greeter service. You'll trigger a build with a misconfigured Dockerfile path, then use AI-assisted workflow inspection and log analysis to diagnose the root cause, compare with the previous successful build, and apply the fix.
53+
54+
**Key MCP tools:** `list_workflow_runs`, `get_workflow_run`, `query_workflow_logs`, `create_workflow_run`
55+
56+
**Time:** ~10 minutes
57+
58+
[View guide on GitHub →](https://github.com/openchoreo/openchoreo/tree/main/samples/mcp/build-failures)
59+
60+
---
61+
62+
### 5. Resource Optimization
63+
64+
Detect and fix over-provisioned deployments in the GCP Microservices Demo (Online Boutique). You'll intentionally allocate excessive CPU and memory to several services, then use AI-assisted analysis to compare allocation vs actual usage, get right-sizing recommendations, and apply optimized configurations.
65+
66+
**Key MCP tools:** `list_components`, `list_release_bindings`, `get_release_binding`, `query_resource_metrics`, `update_release_binding`
67+
68+
**Time:** ~10 minutes
69+
70+
[View guide on GitHub →](https://github.com/openchoreo/openchoreo/tree/main/samples/mcp/resource-optimization)

0 commit comments

Comments
 (0)