kubernetes-clilisted

# Kubernetes CLI Skill Use the context table and rules below when constructing all `kubectl` commands. ## Configuration Update the table below with your kubeconfig context names before using this skill: | Environment | Context Name | Default Namespace | |---|---|---| | Production | `<your-prod-context>` | `<your-prod-namespace>` | | Staging / Non-Prod | `<your-nonprod-context>` | `<your-nonprod-namespace>` | | Sandbox / Dev | `<your-sandbox-context>` | `<your-sandbox-namespace>` | If the target environment is unclear, ask the user before running any command. ### Prerequisites (one-time setup by user) If `kubectl` is not installed or no context is configured for the target cluster, inform the user that setup is required and ask them to complete the following steps manually. Do not perform these steps yourself. ```bash brew install kubectl aws eks update-kubeconfig --name <cluster-name> --profile <profile> --region <region> --alias <your-context-name> # or for other providers, follow the provider-specific kubeconfig setup kubectl config get-contexts ``` ## Command Format Always pass `--context` and `--namespace` explicitly — never rely on the current context or namespace set in kubeconfig: ```bash kubectl <command> --context <context-name> --namespace <namespace> [options] ``` ### Examples ```bash # Production kubectl get pods --context <your-prod-context> --namespace <your-prod-namespace> # Staging / Non-Prod kubectl get pods --context <your-nonprod-context> --na