Deploy and manage TiDB-X clusters on AWS EKS with Terraform and Kubernetes.
npx skills add https://github.com/alex-quan-001/nutshell-skills --skill tidb-onebox
Please help me install this Agent Skill. Skill: tidb-onebox Source: https://github.com/alex-quan-001/nutshell-skills/tree/main/skills/ops/tidb-onebox Command: npx skills add https://github.com/alex-quan-001/nutshell-skills --skill tidb-onebox
Manually provisioning and managing TiDB-X development and test clusters on AWS EKS requires coordinating Terraform, AWS IAM, Kubernetes, and TiDB-specific configurations, which is time-consuming, error-prone, and difficult to reproduce across team members.
Use the tidb-onebox skill to deploy a fully configured TiDB-X development cluster on AWS EKS, run health checks and SQL pushdown verification tests, and safely destroy the environment when you are finished.
High-intent search queries and answers about installing and using this skill.
Automating TiDB cluster deployment on AWS EKS involves wrapping Terraform and Kubernetes operations into a single script to handle provisioning and configuration. This eliminates manual infrastructure setup and configuration drift.
Managing TiDB development environments for SQL pushdown validation requires reproducible clusters on AWS EKS. Automating the lifecycle ensures isolated test environments are spun up quickly and torn down cleanly to avoid cloud costs.
Resolving stuck Kubernetes finalizers and Helm release timeouts during TiDB cluster teardown requires automated failure remediation. This handles common blockers like S3 bucket locks and classic ELB remnants without manual intervention.
You can pause and resume AWS EKS TiDB test clusters to save cloud costs through end-to-end cluster lifecycle management. This supports runtime scaling and health validation for development workflows.
Automated TiDB EKS deployment handles classic ELB remnants and S3 bucket locks through built-in failure remediation. It removes common teardown blockers automatically to ensure clean environment destruction.
Manually provisioning TiDB on Kubernetes leads to configuration drift because coordinating AWS IAM, Terraform, and Kubernetes configurations is error-prone. Automating these operations ensures reproducible environments across team members.
sitharaj88Generate AWS EKS cluster configurations, node groups, Helm charts, and Kubernetes manifests.
alex-quan-001Extract TiDB X cluster growth metrics from BigQuery BI tables.
IldarMinaevValidate pgskipper-operator CRDs, Helm releases, CR statuses, and deployments in Kubernetes clusters.
anyscaleDeploy Anyscale on AWS EKS using Terraform and Helm commands.
