56 test prompts for OpenShift Lightspeed with MCP Server integration — organized by category
checkClusterHealthCheck the overall health of the cluster with detailed information. Show node status, pod health, and any issues found.
checkNodeConditionsCheck all node conditions in the cluster. Are there any nodes with memory pressure, disk pressure, PID pressure, or not ready?
detectResourceIssuesDetect resource issues in the cluster using CPU threshold 80%, memory threshold 85%, and restart threshold 5. Report any problematic pods.
getPerformanceMetricsGet performance metrics for the openshift-lightspeed namespace. Show me CPU and memory usage for all pods.
analyzePodDisruptionsAnalyze pod disruptions in namespace openshift-lightspeed for the last 24 hours. Were there any unexpected restarts, evictions, or OOM kills?
checkKubeletStatusCheck kubelet status on all cluster nodes. Look back 24 hours and include system errors. Show me any nodes where kubelet is unhealthy.
checkCrioStatusCheck CRI-O container runtime status on all nodes. Show recent logs and report any runtime failures.
analyzeJournalctlPodErrorsAnalyze journalctl logs for pod-related errors across the cluster. Look for OOM kills, CrashLoopBackOff, and image pull failures.
monitorDeploymentsMonitor all deployments in the openshift-lightspeed namespace. Show their rollout status, ready replicas, and any unavailable pods.
monitorDeployments (other namespace)Check deployment status in the n8n-test namespace. Are all deployments healthy with all replicas ready?
nodes_topShow me the current CPU and memory usage for all nodes in the cluster. Which node is under the most load?
nodes_logGet the last 50 lines of kubelet logs from node ip-10-0-1-100. Are there any error messages?
nodes_stats_summaryGet detailed resource usage statistics for node ip-10-0-1-100 including CPU, memory, filesystem, network, and PSI metrics.
pods_list_in_namespaceList all pods in the openshift-lightspeed namespace. Show their status, node, and restart count.
pods_listList all pods across the entire cluster. Filter by status to show only pods that are NOT in Running or Succeeded state.
pods_getGet the full details of the pod openshift-mcp-server in namespace openshift-lightspeed. Show me its container images, resource limits, and environment variables.
pods_logGet the last 100 lines of logs from the lightspeed-app-server pod in openshift-lightspeed namespace. Look for any errors or warnings.
pods_topShow me the CPU and memory consumption of all pods in openshift-lightspeed namespace. Which pods are consuming the most resources?
pods_execExecute the command ["cat", "/etc/os-release"] in the openshift-mcp-server pod in namespace openshift-lightspeed. What OS is the container running?
pods_runRun a temporary pod using the image busybox in namespace n8n-test. Name it debug-pod.
namespaces_listList all namespaces in the cluster. Which ones were created by ArgoCD and which are system namespaces?
projects_listList all OpenShift projects in the cluster. How many user projects vs system projects exist?
resources_list — DeploymentsList all deployments in the openshift-lightspeed namespace. Show their replicas and available counts.
resources_list — ServicesList all services in namespace openshift-lightspeed. Show their types and cluster IPs.
resources_list — RoutesList all routes in namespace openshift-lightspeed. Show hostnames and TLS configuration.
resources_list — PVCsList all PersistentVolumeClaims in namespace openshift-lightspeed. Show their status, capacity, and storage class.
resources_list — NetworkPoliciesList all NetworkPolicies in namespace openshift-lightspeed. Explain what traffic is allowed or blocked.
resources_list — ResourceQuotasList all ResourceQuotas in namespace openshift-lightspeed. How close are we to reaching the CPU and memory limits?
resources_list — ConfigMapsList all ConfigMaps in namespace openshift-lightspeed. How many are there and what are their names?
resources_list — SecretsList all Secrets in namespace openshift-lightspeed. Show their types (Opaque, kubernetes.io/tls, etc).
resources_list — HPAList all HorizontalPodAutoscalers in namespace openshift-lightspeed. Show current vs desired replicas and scaling metrics.
resources_list — Operator SubscriptionsList all Subscriptions in namespace openshift-operators with API group operators.coreos.com. Show installed CSV versions and update channels.
resources_list — MCPServerRegistrationsList all MCPServerRegistrations with API group mcp.kuadrant.io in namespace openshift-lightspeed. Show their Ready status and discovered tools count.
resources_get — Specific resourceGet the OLSConfig resource named "cluster" with apiVersion ols.openshift.io/v1alpha1. Show the configured MCP servers and LLM provider.
resources_scale — ScaleScale the deployment n8n in namespace openshift-lightspeed to 2 replicas.
events_listList all events in the openshift-lightspeed namespace. Are there any Warning events related to image pull failures, OOM kills, or CrashLoopBackOff?
events_list (cluster-wide)List all Warning events across all namespaces from the last few minutes. Summarize what went wrong.
createDeploymentCreate a new deployment called httpd-test in namespace n8n-test using image image-registry.openshift-image-registry.svc:5000/openshift/httpd:latest with 2 replicas.
createServiceCreate a ClusterIP service called httpd-test-svc in namespace n8n-test that targets pods with label app=httpd-test, exposing port 8080 to target port 8080.
createHpaCreate a HorizontalPodAutoscaler for deployment httpd-test in namespace n8n-test. Min 1 replica, max 5, scale at 70% CPU and 80% memory.
createNetworkPolicyCreate a deny-all NetworkPolicy in namespace n8n-test for pods with label app=httpd-test. Then create another allowing ingress only from pods with label app=n8n.
deployDatabaseDeploy a PostgreSQL database called test-db in namespace n8n-test for testing purposes.
resources_create_or_update — Direct YAMLCreate a ConfigMap in namespace n8n-test with the following YAML:
apiVersion: v1
kind: ConfigMap
metadata:
name: test-config
namespace: n8n-test
data:
APP_MODE: "production"
LOG_LEVEL: "info"
resources_deleteDelete the deployment called httpd-test in namespace n8n-test. Then verify no pods remain.
pods_deleteDelete the pod openshift-mcp-server-0 in namespace openshift-lightspeed to force a restart. Verify the new pod comes up healthy.
Note: These tools require
kubectlin the MCP pod. Not available in Developer Sandbox.
runCpuStressTestRun a CPU stress test of type load for 30 seconds using 2 cores and 256MB of memory. Show results.
runStorageBenchmarkRun a sequential-read storage benchmark with block size 4k for 30 seconds on a 1Gi volume using the default storage class.
runNetworkTestRun a network bandwidth test using TCP protocol for 30 seconds with 2 parallel streams. Measure throughput.
runDatabaseBenchmarkRun a PostgreSQL oltp_read_write benchmark with 4 threads for 60 seconds on a table with 100000 rows.
runKubeBurnerRun a cluster-density-v2 kube-burner test with 5 iterations in namespace kube-burner-test. Create resources and then clean up.
Give me a complete health report for the openshift-lightspeed namespace:
1. List all running pods and their resource usage
2. Check for any Warning events
3. Monitor deployment rollout status
4. List all routes and services
Something seems wrong in the cluster. Check node conditions, detect resource issues with default thresholds, list recent Warning events across all namespaces, and analyze pod disruptions. Summarize findings.
Give me a full cluster inventory:
1. How many namespaces/projects exist?
2. List all nodes with their CPU/memory usage
3. Check overall cluster health
4. List all Operator Subscriptions and their status
Perform a security audit of namespace openshift-lightspeed:
1. List all NetworkPolicies
2. List all Secrets and their types
3. Check if any pods are running as root
4. List all ServiceAccounts
In namespace n8n-test:
1. Create a deployment called myapp using image nginx:latest with 2 replicas
2. Create a ClusterIP service for it on port 80
3. Create a HPA with min 1 max 5 replicas at 70% CPU
4. Verify everything is running
Check the MCP Gateway infrastructure:
1. List MCPServerRegistrations in openshift-lightspeed namespace (group mcp.kuadrant.io)
2. List MCPGatewayExtensions in mcp-system namespace (group mcp.kuadrant.io)
3. List pods in mcp-system namespace
4. Are all components healthy?