القائمة
Deploy VibeTeam services to k3s, scale worker nodes, and manage node naming (vibe-backend-vm, vibe-worker-0N, k3s-vmss-<suffix>).
التثبيت باستخدام Codex أو Claude انسخ هذا Prompt والصقه في Codex أو Claude أو مساعد آخر ليراجع صفحة Skill ويثبّتها لك.
استنادا إلى تصنيف SOC المهني
Create and configure role-scoped GitHub Apps for VibeTeam, map credentials to agents placeholders, and validate installation permissions/identity.
Run VibeTeam GitHub/Slack handoff validation with unit tests, Slack evals, GitHub webhook evals, and permission checks. Use when validating multi-agent GitHub communication (issues, discussions, PR comments) or when asked to prove changes via tests/evals and record status.
Create and configure VibeTeam Slack apps (one ingress app plus role-scoped responder apps), wire role tokens/secrets, and validate routing/identity behavior.
Final completion gate for VibeTeam tasks. Use at the end of implementation to verify diff quality, real testing, GitHub/Slack multi-agent communication evidence, and PR health before declaring done.
Search shared knowledgebase content using docs_tools (BM25 + fallback keyword scoring) before answering from memory.
Shared workflow for knowledgebase retrieval using docs_tools and injected OpenClaw context.
| name | k3s-ops |
| description | Deploy VibeTeam services to k3s, scale worker nodes, and manage node naming (vibe-backend-vm, vibe-worker-0N, k3s-vmss-<suffix>). |
kubectl apply -k k8s/overlays/dev
# or
kubectl apply -k k8s/overlays/prod
Validate rollouts:
kubectl rollout status deployment/openhands-svc -n vibeteam --timeout=180s
kubectl get pods -n vibeteam
Edit services/k3s/terraform/variables.tf:
worker_countThen apply:
cd services/k3s/terraform
terraform init
terraform plan
terraform apply
Enable VMSS:
cd services/k3s/terraform
terraform apply -var 'enable_vmss=true'
Deploy autoscaler:
cd services/k3s/manifests
./setup-autoscaler.sh
Set bounds in services/k3s/terraform/variables.tf:
vmss_min_countvmss_max_countvibe-backend-vmvibe-worker-0N from node_name in cloud-init-worker.yaml and VM name in services/k3s/terraform/main.tf.k3s-vmss-<suffix> from NODE_NAME in cloud-init-vmss.yaml.Renaming is not in-place. To rename:
kubectl drain <old-node> --ignore-daemonsets --delete-emptydir-datakubectl delete node <old-node>node_name / cloud-init-vmss.yaml).If you need strict names like k3s-node-1..N, use standalone workers (static node_name). VMSS names are derived and should stay pattern-based.