tundra-dome

Validate the Tundra Dome stack across local and KIND Kubernetes environments.

1|Updated Jul 16, 2025
One-click install
npx skills add https://github.com/ryanmaclean/vibecode-webgui --skill tundra-dome
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: tundra-dome
Source: https://github.com/ryanmaclean/vibecode-webgui/tree/main/skills/tundra-dome
Command: npx skills add https://github.com/ryanmaclean/vibecode-webgui --skill tundra-dome

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill includes scripts (resource) and references (resource) components.

What problem does it solve?

Standardizes bead/PR/issue flow across Gas Town → Tundra Dome, enabling consistent deployment, validation, and observability of the Tundra Dome stack (Kafka, Airflow, Datadog) in both local environments and KIND.

Core Features & Use Cases

  • Lane routing, KPI snapshots, and Datadog dashboard validation
  • Quick Tundra Dome rollout checks across hosts
  • Kubernetes-based deployment bootstrap for local and KIND environments

Quick Start

Install prerequisites (bd, gt, kubectl, kind, docker, and the datadog-agent CLI if available).

To bootstrap the environment:

  • Create namespaces: kubectl create ns tundra-dome && kubectl create ns datadog
  • Create secrets: kubectl -n tundra-dome create secret generic tundra-dome-secrets --from-literal=DD_API_KEY=$DD_API_KEY --dry-run=client -o yaml | kubectl apply -f -
  • kubectl -n datadog create secret generic tundra-dome-secrets --from-literal=DD_API_KEY=$DD_API_KEY --dry-run=client -o yaml | kubectl apply -f -
  • kubectl apply -f infra/tundra-dome/tundra-dome.clean.yaml
  • kubectl get pods -n tundra-dome -w Representative quick actions:
  • Issue → bead sync (GitHub/Gitea): Set GITHUB_DRY_RUN=true to test; run daemon/kafka-dsm/github-issue-dispatcher.sh; then set GITHUB_DRY_RUN=false for live runs.
  • Lane routing: Update labels to tundra-lane-* beads and adjust related config (airflow/dags and dispatcher scripts).
  • KPI snapshot + DD checks: Run python3 daemon/kpi_snapshot.py and verify td_event_emitter metrics.
  • Kafka health: Use td-kafka tools to verify topics and consumer groups.
  • Launchd services: Restart services via launchctl and inspect logs.
  • OpenCode/OpenRouter notes: Optional integration steps exist for model-based deployments.

Frequently Asked Questions about tundra-dome

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I bootstrap Kafka and Airflow deployment in a local KIND environment?

You can validate Kafka health locally by using td-kafka tools to verify topics and consumer groups, running python3 daemon/kpi_snapshot.py for KPI snapshots, and checking td_event_emitter metrics through the Datadog agent.

Do I need kubectl and kind installed to run local Kubernetes deployment validation?

Yes, you need kubectl and kind installed to run local Kubernetes deployment validation, along with docker, bd, gt, and optionally the datadog-agent CLI for full observability and health check coverage.

How does GitHub issue sync work with Kafka dispatchers for deployment automation?

GitHub issue sync works with Kafka dispatchers by running the github-issue-dispatcher shell script, initially setting GITHUB_DRY_RUN=true to test the bead flow, then switching to false for live deployment automation runs.

Can I validate Datadog dashboards and KPI metrics across local and KIND environments?

You can validate Datadog dashboards and KPI metrics across local and KIND environments by running python3 daemon/kpi_snapshot.py, verifying td_event_emitter metrics, and monitoring pods through the Datadog agent in both setups.

What is the best way to manage Kubernetes secrets for Datadog across multiple namespaces?

The best way to manage Kubernetes secrets for Datadog across multiple namespaces is creating a generic secret with your DD_API_KEY using kubectl, then piping the dry-run output to kubectl apply for both tundra-dome and datadog namespaces.