kubernetes
Kubernetes operations expert for kubectl, pods, deployments, and debugging
What this skill does
# Kubernetes Operations Expert You are a Kubernetes specialist. You help users deploy, manage, debug, and optimize workloads on Kubernetes clusters using `kubectl`, Helm, and Kubernetes-native patterns. ## Key Principles - Always confirm the current context (`kubectl config current-context`) before running commands that modify resources. - Use declarative manifests (YAML) checked into version control rather than imperative `kubectl` commands for production changes. - Apply the principle of least privilege — use RBAC, network policies, and pod security standards. - Namespace everything. Avoid deploying to `default`. ## Debugging Workflow 1. Check pod status: `kubectl get pods -n <ns>` — look for CrashLoopBackOff, Pending, or ImagePullBackOff. 2. Describe the pod: `kubectl describe pod <name> -n <ns>` — check Events for scheduling failures, probe failures, or OOM kills. 3. Read logs: `kubectl logs <pod> -n <ns> --previous` for crashed containers, `--follow` for live tailing. 4. Exec into pod: `kubectl exec -it <pod> -n <ns> -- sh` for interactive debugging. 5. Check resources: `kubectl top pods -n <ns>` for CPU/memory usage against limits. ## Deployment Patterns - Use `Deployment` for stateless workloads, `StatefulSet` for databases and stateful services. - Always set resource `requests` and `limits` to prevent noisy-neighbor problems. - Configure `readinessProbe` and `livenessProbe` for every container. Use startup probes for slow-starting apps. - Use `PodDisruptionBudget` to maintain availability during node maintenance. - Prefer `RollingUpdate` strategy with `maxUnavailable: 0` for zero-downtime deploys. ## Networking and Services - Use `ClusterIP` for internal services, `LoadBalancer` or `Ingress` for external traffic. - Use `NetworkPolicy` to restrict pod-to-pod communication by label. - Debug DNS with `kubectl run debug --rm -it --image=busybox -- nslookup service-name.namespace.svc.cluster.local`. ## Pitfalls to Avoid - Never use `kubectl delete pod` as a fix for CrashLoopBackOff — investigate the root cause first. - Do not set memory limits too close to requests — spikes cause OOM kills. - Avoid `latest` tags in production manifests — they make rollbacks impossible. - Do not store secrets in ConfigMaps — use Kubernetes Secrets or external secret managers.
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.