eks-operation-review
starsforks
How to install eks-operation-review?
aws-samples/sample-devops-agent-tools/eks-operation-review
$npx -y skills add aws-samples/sample-devops-agent-tools --skill eks-operation-reviewComprehensive Amazon EKS operational review aligned with the AWS EKS
SKILL.md
| 1 | # EKS Operational Review |
| 2 | |
| 3 | Conduct a comprehensive operational review of Amazon EKS clusters aligned with the |
| 4 | [EKS Best Practices Guide](https://docs.aws.amazon.com/eks/latest/best-practices/introduction.html). |
| 5 | |
| 6 | ## When to Use |
| 7 | |
| 8 | Activate this skill when the user asks to: |
| 9 | - Review, audit, or assess EKS clusters |
| 10 | - Check EKS best practices compliance |
| 11 | - Evaluate EKS security, cost, reliability, networking, or scalability |
| 12 | - Perform an EKS operational readiness review |
| 13 | - Investigate EKS cluster health or configuration |
| 14 | |
| 15 | ## Step 1: Identify Target Clusters |
| 16 | |
| 17 | Ask the user which EKS clusters to review. Accept: |
| 18 | - Specific cluster names and regions |
| 19 | - "all clusters" in specific regions |
| 20 | - "all clusters in all regions" |
| 21 | |
| 22 | Use the EKS topology data available in the Agent Space to identify clusters. |
| 23 | Query CloudWatch and AWS APIs to discover clusters: |
| 24 | - List EKS clusters across the configured account regions |
| 25 | - For each cluster, collect configuration details |
| 26 | |
| 27 | ## Step 2: Collect Cluster Configuration |
| 28 | |
| 29 | **Data source priority**: If Kubernetes API access is available (via connected MCP servers such as kubernetes-mcp-server, EKS MCP server, or direct K8s API tools), use it FIRST to get live cluster state. K8s API provides the most accurate, real-time data. Fall back to AWS APIs and CloudWatch only for data not available via K8s API. |
| 30 | |
| 31 | **K8s API tools** (use first when available): |
| 32 | - `resources_list` / `resources_get` — list/read any K8s resource by apiVersion and kind |
| 33 | - `pods_list` / `pods_get` / `pods_log` / `pods_top` — pod operations |
| 34 | - `nodes_top` — node resource usage |
| 35 | - `events_list` — K8s events |
| 36 | - `configuration_contexts_list` — available cluster contexts |
| 37 | |
| 38 | For EACH cluster, gather the following data. **Try K8s API first, then AWS API as fallback**: |
| 39 | |
| 40 | ### 2.1 EKS Cluster Config |
| 41 | **AWS API** (no K8s equivalent): Kubernetes version, platform version, control plane logging, secrets encryption, endpoint access, authentication mode, access entries, Auto Mode, tags |
| 42 | |
| 43 | ### 2.2 Node Groups & Compute |
| 44 | **K8s API first**: |
| 45 | - `resources_list(apiVersion="v1", kind="Node")` — live node list with labels, capacity, allocatable, conditions |
| 46 | - `nodes_top` — actual CPU/memory usage per node |
| 47 | - `resources_list(apiVersion="karpenter.sh/v1", kind="NodePool")` — Karpenter NodePools |
| 48 | - `resources_get(apiVersion="karpenter.sh/v1", kind="NodePool", name=<name>)` — full NodePool spec (consolidation, limits, disruption, requirements) |
| 49 | - `resources_list(apiVersion="karpenter.k8s.aws/v1", kind="EC2NodeClass")` — EC2NodeClasses |
| 50 | - `resources_get(apiVersion="karpenter.k8s.aws/v1", kind="EC2NodeClass", name=<name>)` — full spec (amiFamily, blockDeviceMappings, metadataOptions, subnets, SGs) |
| 51 | |
| 52 | **AWS API fallback**: Managed node groups (instance types, scaling config, AMI type, capacity type, AZ distribution) |
| 53 | |
| 54 | ### 2.3 Add-ons |
| 55 | **K8s API first**: |
| 56 | - `resources_list(apiVersion="apps/v1", kind="Deployment", namespace="kube-system")` — all system deployments with image versions |
| 57 | - `resources_list(apiVersion="apps/v1", kind="DaemonSet", namespace="kube-system")` — all system daemonsets with image versions |
| 58 | |
| 59 | **AWS API fallback**: EKS managed add-ons (name, version, status, health) |
| 60 | |
| 61 | ### 2.4 Networking |
| 62 | **K8s API first**: |
| 63 | - `resources_get(apiVersion="apps/v1", kind="DaemonSet", name="aws-node", namespace="kube-system")` — VPC CNI config (env vars: ENABLE_PREFIX_DELEGATION, WARM_IP_TARGET, etc.) |
| 64 | - `resources_get(apiVersion="v1", kind="ConfigMap", name="coredns", namespace="kube-system")` — CoreDNS Corefile |
| 65 | - `resources_get(apiVersion="apps/v1", kind="Deployment", name="coredns", namespace="kube-system")` — CoreDNS replicas, resources, topology |
| 66 | - `resources_list(apiVersion="networking.k8s.io/v1", kind="NetworkPolicy")` — network policies |
| 67 | - `resources_list(apiVersion="v1", kind="Service")` — services and load balancers |
| 68 | |
| 69 | **AWS API** (no K8s equivalent): VPC CIDR, subnet IP availability, security groups, VPC endpoints, NAT gateways |
| 70 | |
| 71 | ### 2.5 Security |
| 72 | **K8s API first**: |
| 73 | - `resources_list(apiVersion="rbac.authorization.k8s.io/v1", kind="ClusterRoleBinding")` — RBAC bindings (check cluster-admin, system:anonymous) |
| 74 | - `resources_list(apiVersion="rbac.authorization.k8s.io/v1", kind="ClusterRole")` — roles with wildcard permissions |
| 75 | - `resources_get(apiVersion="v1", kind="Co |
People who liked this also viewed
6 picksType
- microsoft-foundryDeploy, evaluate, fine-tune, and manage Foundry agents end-to-end with azd: hosted agent scaffold/run/deploy, prompt agent create, batch eval, continuous eval, prompt optimizer, Agent Optimizer scaffoSkillsJul 2026
- azure-deployExecute Azure deployments for ALREADY-PREPARED applications that have existing .azure/deployment-plan.md and infrastructure files. DO NOT use this skill when the user asks to CREATE a new application SkillsJul 2026
- azure-preparePrepare azd-based Azure projects for deployment: generates azure.yaml, infrastructure (Bicep/Terraform), and Dockerfiles for the Azure Developer CLI (azd) workflow. USE ONLY when the user explicitly wSkillsJul 2026
- azure-validate--- name: azure-validate description: "Pre-deployment validation for Azure readiness. Run deep checks on configuration, infrastructure (Bicep or Terraform), RBAC role assignments, managed identity pSkillsJul 2026
- azure-aigatewayConfigure Azure API Management as an AI Gateway for AI models, MCP tools, and agents. WHEN: semantic caching, token limit, content safety, load balancing, AI model governance, MCP rate limiting, jailbSkillsJul 2026
- azure-hosted-copilot-sdkOfficial agent plugin providing skills and MCP server configurations for Azure scenarios.SkillsJul 2026
