local:testing
SkillCloud & infraTest Rossoctl platform locally using Kind. Scripts for deploy, test, and access.
Available today. Use it from your connected AI after setup.
No other account needed.
Connect ahel once, and every AI you use reads what you have installed.
Then ask your AI: use the local:testing skill
What this skill tells your AI
The instructions your AI receives, as published by rossoctl/rossoctl in .claude/skills/local:testing/SKILL.md and read by ahel’s review.
This skill helps you test Rossoctl platform locally using Kind (Kubernetes in Docker).
Overview
The local-testing/ directory contains scripts that mirror the GitHub Actions CI workflow, allowing you to:
- Deploy the full Rossoctl platform locally
- Run E2E tests with Ollama LLM integration
- Access the Rossoctl UI and services
- Debug agent and tool deployments
Prerequisites
Ensure you have:
- Docker Desktop/Rancher Desktop/Podman (12GB RAM, 4 cores minimum)
- Kind, kubectl, helm installed
- Python 3.11+ with uv
- jq for JSON parsing
Available Scripts
1. Cleanup Cluster
Wipes the existing Kind cluster completely:
./local-testing/cleanup-cluster.sh
Use this when you want a fresh start or cluster is in a bad state.
2. Deploy Platform
Deploys the full Rossoctl platform (takes ~15-20 minutes):
./local-testing/deploy-platform.sh
This script:
- Creates Kind cluster via bash installer
- Deploys all platform components (Keycloak, PostgreSQL, Istio, SPIRE)
- Installs Ollama and pulls qwen2.5:0.5b model
- Deploys weather agent and tool
3. Run E2E Tests
Runs the E2E test suite:
./local-testing/run-e2e-tests.sh
Validates:
- Platform deployment health
- Agent conversation via A2A protocol
- Ollama LLM integration
- MCP tool invocation
4. Access UI
Shows access information and port-forward commands:
./local-testing/access-ui.sh
Then run the suggested command:
kubectl port-forward -n rossoctl-system svc/http-istio 8080:80
Visit: http://rossoctl-ui.localtest.me:8080
Typical Workflow
Full Redeploy and Test
# 1. Clean up existing cluster
./local-testing/cleanup-cluster.sh
# 2. Deploy platform (wait ~15-20 minutes)
./local-testing/deploy-platform.sh
# 3. Run E2E tests
./local-testing/run-e2e-tests.sh
# 4. Access UI
./local-testing/access-ui.sh
Quick Test Iteration
If platform is already deployed and you just want to rerun tests:
./local-testing/run-e2e-tests.sh
Development Cycle
- Make code changes
- Run
./local-testing/deploy-platform.shto redeploy - Run
./local-testing/run-e2e-tests.shto validate - Use
./local-testing/access-ui.shto get UI access
Debugging Commands
View Logs
# Agent logs
kubectl logs -n team1 deployment/weather-service --tail=100 -f
# Tool logs
kubectl logs -n team1 deployment/weather-tool --tail=100 -f
# Platform operator
kubectl logs -n rossoctl-system deployment/rossoctl-platform-operator --tail=100 -f
Check Pod Status
# All pods
kubectl get pods -A
# Specific namespace
kubectl get all -n team1
kubectl get all -n rossoctl-system
View Events
# Recent events in team1 namespace
kubectl get events -n team1 --sort-by='.lastTimestamp' | tail -30
# All events
kubectl get events -A --sort-by='.lastTimestamp' | tail -50
Ollama Status
# Check if running
ps aux | grep ollama
# Check models
ollama list
# Test directly
curl http://localhost:11434/api/tags
Troubleshooting
Platform Not Ready
If deployment times out or components aren't ready:
# Check pod status
kubectl get pods -A
# Check recent events
kubectl get events -A --sort-by='.lastTimestamp' | tail -50
# Retry deployment
./local-testing/cleanup-cluster.sh
./local-testing/deploy-platform.sh
Test Failures
If E2E tests fail:
- Check agent logs:
kubectl logs -n team1 deployment/weather-service --tail=100 - Check tool logs:
kubectl logs -n team1 deployment/weather-tool --tail=100 - Verify Ollama is running:
ps aux | grep ollama - Check Ollama has model:
ollama list | grep qwen2.5
UI Access Issues
If UI doesn't load:
- Verify pod is running:
kubectl get pods -n rossoctl-system -l app=rossoctl-ui - Check Istio gateway:
kubectl get pods -n rossoctl-system -l app=http-istio - Restart port-forward:
kubectl port-forward -n rossoctl-system svc/http-istio 8080:80
Notes
- These scripts are for local development only (not committed to repo)
- Scripts are in
.gitignoreto avoid accidental commits - Deployment uses same installer as CI
- Cluster name is
rossoctl(matches CI workflow) - Secrets used are test values (not production)
Files Location
All scripts are in: local-testing/
cleanup-cluster.sh- Wipe clusterdeploy-platform.sh- Deploy platformrun-e2e-tests.sh- Run testsaccess-ui.sh- Access informationREADME.md- Full documentation
Related Skills
local:full-test- Complete test workflows for Kind and HyperShiftkind:cluster- Create/destroy Kind clustersrossoctl:deploy- Deploy platform
Signals
- GitHub stars
- 301
- Forks
- 107
- Last commit
- Sep 2026
Advanced
- Catalog kind
- skill
- Gateway key
local-testing- Source
- github.com/rossoctl/rossoctl