auth
무료Authentication and authorization patterns for Rossoctl services
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Test Rossoctl platform locally using Kind. Scripts for deploy, test, and access.
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
실행 점수 미검증
설치 방법 보기설치하기 전에 에이전트에게 전달되는 지시 내용을 확인할 수 있습니다.
This skill helps you test Rossoctl platform locally using Kind (Kubernetes in Docker).
The local-testing/ directory contains scripts that mirror the GitHub Actions CI workflow, allowing you to:
Ensure you have:
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.
Deploys the full Rossoctl platform (takes ~15-20 minutes):
./local-testing/deploy-platform.sh
This script:
Runs the E2E test suite:
./local-testing/run-e2e-tests.sh
Validates:
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
# 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
If platform is already deployed and you just want to rerun tests:
./local-testing/run-e2e-tests.sh
./local-testing/deploy-platform.sh to redeploy./local-testing/run-e2e-tests.sh to validate./local-testing/access-ui.sh to get UI access# 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
# All pods
kubectl get pods -A
# Specific namespace
kubectl get all -n team1
kubectl get all -n rossoctl-system
# 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
# Check if running
ps aux | grep ollama
# Check models
ollama list
# Test directly
curl http://localhost:11434/api/tags
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
If E2E tests fail:
kubectl logs -n team1 deployment/weather-service --tail=100kubectl logs -n team1 deployment/weather-tool --tail=100ps aux | grep ollamaollama list | grep qwen2.5If UI doesn't load:
kubectl get pods -n rossoctl-system -l app=rossoctl-uikubectl get pods -n rossoctl-system -l app=http-istiokubectl port-forward -n rossoctl-system svc/http-istio 8080:80.gitignore to avoid accidental commitsrossoctl (matches CI workflow)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 documentationlocal:full-test - Complete test workflows for Kind and HyperShiftkind:cluster - Create/destroy Kind clustersrossoctl:deploy - Deploy platform아직 리뷰가 없습니다. 사용해 본 소감을 남겨 주세요.
로그인 없이 쓸 수 있습니다. 사용 후기, 질문, 작동하지 않은 환경 등을 편하게 남겨 주세요.
아직 댓글이 없습니다. 첫 댓글을 남겨 보세요.
Authentication and authorization patterns for Rossoctl services
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Create confidential OAuth2 clients in Keycloak for server-to-service authentication
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Configure MLflow with mlflow-oidc-auth plugin for Keycloak OIDC authentication
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Configure OpenTelemetry Collector with OAuth2 authentication for trace export
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
CI pipeline monitoring, status checks, and PR validation workflows
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.
Monitor running CI jobs, wait for completion, create tasks for results
한국어 요약은 준비 중입니다. 원문 설명을 표시하고 있습니다.