castai-deploy-integration
Deploy CAST AI across multi-cloud Kubernetes clusters with Terraform modules. Use when onboarding EKS, GKE, or AKS clusters to CAST AI using infrastructure-as-code patterns. Trigger with phrases like "deploy cast ai", "cast ai eks", "cast ai gke", "cast ai aks", "cast ai terraform module".
What this skill does
# CAST AI Deploy Integration
## Overview
Deploy CAST AI to EKS, GKE, and AKS clusters using official Terraform modules. Each cloud provider has a dedicated CAST AI module that handles IAM roles, node configuration, and autoscaler setup.
## Prerequisites
- Terraform 1.0+
- CAST AI Full Access API key
- Cloud provider credentials configured
- Existing Kubernetes cluster
## Instructions
### EKS Deployment
```hcl
# main.tf -- EKS cluster onboarding
module "castai_eks" {
source = "castai/eks-cluster/castai"
version = "~> 3.0"
api_token = var.castai_api_token
aws_account_id = data.aws_caller_identity.current.account_id
aws_cluster_region = var.region
aws_cluster_name = var.cluster_name
# IAM role for CAST AI to manage nodes
aws_instance_profile_arn = aws_iam_instance_profile.castai.arn
# Autoscaler configuration
autoscaler_policies_json = jsonencode({
enabled = true
unschedulablePods = { enabled = true }
nodeDownscaler = {
enabled = true
emptyNodes = { enabled = true, delaySeconds = 300 }
}
spotInstances = {
enabled = true
spotDiversityEnabled = true
}
clusterLimits = {
enabled = true
cpu = { minCores = 4, maxCores = 200 }
}
})
# Node templates
default_node_configuration = module.castai_eks.castai_node_configurations["default"]
}
```
### GKE Deployment
```hcl
module "castai_gke" {
source = "castai/gke-cluster/castai"
version = "~> 2.0"
api_token = var.castai_api_token
project_id = var.gcp_project_id
gke_cluster_name = var.cluster_name
gke_cluster_location = var.region
gke_credentials = base64decode(
google_container_cluster.this.master_auth[0].cluster_ca_certificate
)
autoscaler_policies_json = jsonencode({
enabled = true
unschedulablePods = { enabled = true }
nodeDownscaler = {
enabled = true
emptyNodes = { enabled = true, delaySeconds = 300 }
}
})
}
```
### AKS Deployment
```hcl
module "castai_aks" {
source = "castai/aks/castai"
version = "~> 1.0"
api_token = var.castai_api_token
aks_cluster_name = var.cluster_name
aks_cluster_region = var.region
node_resource_group = azurerm_kubernetes_cluster.this.node_resource_group
azure_subscription_id = data.azurerm_subscription.current.subscription_id
azure_tenant_id = data.azurerm_client_config.current.tenant_id
autoscaler_policies_json = jsonencode({
enabled = true
unschedulablePods = { enabled = true }
spotInstances = { enabled = true }
})
}
```
### Multi-Cluster Deployment Pattern
```hcl
# Deploy CAST AI across all clusters with a for_each
variable "clusters" {
type = map(object({
name = string
provider = string # eks, gke, aks
region = string
max_cpu = number
}))
}
# Then reference the appropriate module per provider
```
## Error Handling
| Issue | Cause | Solution |
|-------|-------|----------|
| IAM role error | Missing permissions | Check CAST AI IAM docs for required policies |
| Module version conflict | Terraform lock | Run `terraform init -upgrade` |
| Cluster not appearing | Wrong credentials | Verify cloud provider auth |
| Policies not applying | JSON encoding error | Validate `jsonencode()` output |
## Resources
- [EKS Module](https://registry.terraform.io/modules/castai/eks-cluster/castai/latest)
- [GKE Module](https://registry.terraform.io/modules/castai/gke-cluster/castai/latest)
- [AKS Module](https://registry.terraform.io/modules/castai/aks/castai/latest)
- [CAST AI Terraform Provider](https://registry.terraform.io/providers/castai/castai/latest/docs)
## Next Steps
For webhook-based automation, see `castai-webhooks-events`.
Related in Cloud & DevOps
appbuilder-action-scaffolder
IncludedCreate, implement, deploy, and debug Adobe Runtime actions with consistent layout, validation, and error handling. Use this skill whenever the user needs to add actions to an App Builder project, understand action structure (params, response format, web/raw actions), configure actions in the manifest, use App Builder SDKs (State, Files, Events, database), deploy and invoke actions via CLI, debug action issues, or implement patterns such as webhook receivers, custom event providers, journaling consumers, large payload redirects, action sequence pipelines, and Asset Compute workers. Also trigger when users mention serverless functions in Adobe context, action logging, IMS authentication for actions, or cron-style scheduled actions.
orchestrating-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. Use this skill when the user needs a multi-step Data Cloud pipeline, cross-phase troubleshooting, or data space and data kit management. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase sf data360 workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching phase-specific skill), the task is STDM/session tracing/parquet telemetry (use observing-agentforce), standard CRM SOQL (use querying-soql), or Apex implementation (use generating-apex).
github-project-automation
IncludedAutomate GitHub repository setup with CI/CD workflows, issue templates, Dependabot, and CodeQL security scanning. Includes 12 production-tested workflows and prevents 18 errors: YAML syntax, action pinning, and configuration. Use when: setting up GitHub Actions CI/CD, creating issue/PR templates, enabling Dependabot or CodeQL scanning, deploying to Cloudflare Workers, implementing matrix testing, or troubleshooting YAML indentation, action version pinning, secrets syntax, runner versions, or CodeQL configuration. Keywords: github actions, github workflow, ci/cd, issue templates, pull request templates, dependabot, codeql, security scanning, yaml syntax, github automation, repository setup, workflow templates, github actions matrix, secrets management, branch protection, codeowners, github projects, continuous integration, continuous deployment, workflow syntax error, action version pinning, runner version, github context, yaml indentation error
sf-datacloud
IncludedSalesforce Data Cloud product orchestrator for connect→prepare→harmonize→segment→act workflows. TRIGGER when: user needs a multi-step Data Cloud pipeline, asks to set up or troubleshoot Data Cloud across phases, manages data spaces or data kits, or wants a cross-phase `sf data360` workflow. DO NOT TRIGGER when: work is isolated to a single phase (use the matching sf-datacloud-* skill), the task is STDM/session tracing/parquet telemetry (use sf-ai-agentforce-observability), standard CRM SOQL (use sf-soql), or Apex implementation (use sf-apex).
fabric-cli
IncludedUse this skill for Fabric.so CLI workflows with the `fabric` terminal command: diagnose/install/login, search or browse a Fabric library, save notes/links/files, create folders, ask the Fabric AI assistant, manage tasks/workspaces, generate shell completion, check subscription usage, produce JSON output, and use Fabric as persistent agent memory. Do not use for Microsoft Fabric/Azure/Power BI `fab`, Daniel Miessler's Fabric framework, Python Fabric SSH, Fabric.js, or textile/fashion fabric.
lark
IncludedLark/Feishu CLI skills: lark-cli operations for docs, markdown, sheets, base, calendar, im, mail, task, okr, drive, wiki, slides, whiteboard, apps, approval, attendance, contact, vc, minutes, event. Use when the user needs to operate Lark/Feishu resources via lark-cli, send messages, manage documents, spreadsheets, calendars, tasks, OKRs, deploy web pages, or any Feishu/Lark workspace operations.