kubectl
Manage Kubernetes resources, contexts, and workloads with kubectl. Use when tasks mention kubectl, Kubernetes resources, kubeconfig, kubectl apply, kubectl get pods, Kubernetes contexts, or KUBECONFIG.
What this skill does
# kubectl Use this skill to keep Kubernetes resource management deterministic and safe across clusters and namespaces. ## Intent Router | Request | Reference | Load When | | --- | --- | --- | | Install, kubeconfig setup, contexts, env vars | `resources/install-and-setup.md` | User needs to install kubectl or configure KUBECONFIG/contexts | | Core commands: get/describe/apply/delete/logs/exec | `resources/command-cookbook.md` | User needs daily kubectl operations | | Resources, labels, namespaces, explain | `resources/resource-management.md` | User asks about resource types, labels, selectors, or declarative workflows | | Pod crashes, ImagePull errors, events, debug | `resources/troubleshooting.md` | User encounters CrashLoopBackOff, OOMKilled, or needs cluster diagnostics | ## Quick Start ```bash # Verify connectivity kubectl cluster-info kubectl get nodes # Confirm active context and namespace kubectl config current-context kubectl config view --minify # List pods in all namespaces kubectl get pods -A # Apply a manifest kubectl apply -f deployment.yaml --dry-run=client kubectl apply -f deployment.yaml ``` ## Core Command Tracks - **Read state:** `kubectl get/describe <resource>` — inspect current cluster state - **Apply changes:** `kubectl apply -f` — declarative reconciliation - **Logs:** `kubectl logs <pod> [-c <container>] [-f] [--previous]` - **Shell:** `kubectl exec -it <pod> -- bash` - **Port forward:** `kubectl port-forward <pod> 8080:80` - **Rollout:** `kubectl rollout status/history/undo deployment/<name>` - **Scale:** `kubectl scale deployment/<name> --replicas=3` - **Output formats:** `-o wide`, `-o json`, `-o yaml`, `-o jsonpath` ## Safety Guardrails - Always confirm active context (`kubectl config current-context`) before applying changes to prevent applying to the wrong cluster. - Always specify namespace explicitly with `-n <namespace>` for production operations; never rely on default namespace alone. - Use `--dry-run=client -o yaml` to preview resources before applying. - Use `kubectl diff -f <file>` to see what will change before applying. - Confirm before running `kubectl delete` — especially with label selectors (`-l`) which can match many resources. - Never run `kubectl delete namespace <name>` without explicit user confirmation; it deletes all resources in the namespace. - Prefer `kubectl rollout undo` over direct manifest rewrites for reverting deployments. ```bash # Troubleshoot a crashing pod: check recent events then inspect previous container logs kubectl get events --sort-by=.lastTimestamp -n my-namespace kubectl logs my-pod --previous -n my-namespace ``` ## Workflow 1. Confirm context: `kubectl config current-context` and `kubectl config get-contexts`. 2. Inspect current state with `kubectl get` and `kubectl describe` before making changes. 3. Preview changes with `kubectl diff -f <file>` or `--dry-run=client`. 4. Apply changes with `kubectl apply -f <file>`. 5. Monitor rollout with `kubectl rollout status deployment/<name>`. 6. On failure, check events with `kubectl get events --sort-by=.lastTimestamp`. ## Related Skills - **helm** — package manager for Kubernetes applications - **docker** — container image building for Kubernetes workloads ## References - `resources/install-and-setup.md` - `resources/command-cookbook.md` - `resources/resource-management.md` - `resources/troubleshooting.md` - Official docs: <https://kubernetes.io/docs/reference/kubectl/> - Command reference: <https://kubernetes.io/docs/reference/generated/kubectl/kubectl-commands>
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.