# Use Eks Via Call Kubectl

> Use when any task involves inspecting EKS pod status, pod events,

- **Type:** Skill
- **Install:** `agentstack add skill-aws-samples-sample-skills-for-aws-devops-agent-use-eks-via-call-kubectl`
- **Verified:** Yes — security-reviewed for prompt injection and unsafe behavior
- **Seller:** [aws-samples](https://agentstack.voostack.com/s/aws-samples)
- **Installs:** 0
- **Category:** [Agent Skills](https://agentstack.voostack.com/c/agent-skills)
- **Latest version:** 0.1.0
- **License:** MIT
- **Upstream author:** [aws-samples](https://github.com/aws-samples)
- **Source:** https://github.com/aws-samples/sample-skills-for-AWS-Devops-agent/tree/main/devops-agent-cn-management/use-eks-via-call-kubectl

## Install

```sh
agentstack add skill-aws-samples-sample-skills-for-aws-devops-agent-use-eks-via-call-kubectl
```

Requires the [AgentStack CLI](https://agentstack.voostack.com/docs/cli). Works with Claude Code, Cursor, and any MCP-compatible agent.

## About

# EKS Inspection via call_kubectl (China Region)

## Why `use_kubectl` fails here

`use_kubectl` is a platform-level tool with a hardcoded account allowlist
limited to the global (`aws`) partition. The cluster `bjs-web` lives in
account `107422471498`, `cn-north-1` (`aws-cn` partition). Token-based EKS
authentication cannot cross partition boundaries.

**Do not retry `use_kubectl` with any account ID. It will never work.**

## The correct tool: `call_kubectl`

The `aws-cn-2` MCP server exposes a `call_kubectl` tool alongside `call_aws`.
Same connection, same endpoint — no additional MCP server needed.

Allowed verbs: `get`, `describe`, `logs`, `top`, `explain`,
`version`, `cluster-info`, `api-resources`, `api-versions`

Write verbs (`apply`, `delete`, `patch`, `exec`, etc.) are blocked by the
tool itself — output them as a draft command for human approval instead.

## Common substitutions

| Original intent | Use this instead |
|---|---|
| `kubectl get pods -n bjs-web -o wide` | `call_kubectl("kubectl get pods -n bjs-web -o wide")` |
| `kubectl describe pod  -n bjs-web` | `call_kubectl("kubectl describe pod  -n bjs-web")` |
| `kubectl logs  -n bjs-web --since=1h` | `call_kubectl("kubectl logs  -n bjs-web --since=1h")` |
| `kubectl get events -n bjs-web --sort-by=.lastTimestamp` | `call_kubectl("kubectl get events -n bjs-web --sort-by=.lastTimestamp")` |
| `kubectl get deployments -n bjs-web` | `call_kubectl("kubectl get deployments -n bjs-web")` |

## Standard incident investigation sequence

For a pod-not-ready alarm on bjs-web:

```
# 1. Pod overview
call_kubectl("kubectl get pods -n bjs-web -o wide")

# 2. For any non-Running pod, describe it
call_kubectl("kubectl describe pod  -n bjs-web")

# 3. Events (sorted by time)
call_kubectl("kubectl get events -n bjs-web --sort-by=.lastTimestamp")

# 4. Deployment status
call_kubectl("kubectl get deployments -n bjs-web")

# 5. Logs if pod is running or was recently running
call_kubectl("kubectl logs  -n bjs-web --since=30m")
```

## Failure pattern quick reference

| What you see in describe/events | Root cause |
|---|---|
| `ImagePullBackOff` / `ErrImagePull` | Image tag does not exist in ECR — fault L6 |
| `OOMKilled` | Memory limit hit — fault L9 neighbourhood |
| `CrashLoopBackOff` | Container exits — check logs next |
| `Insufficient cpu` / `Insufficient memory` | Node resource exhausted |
| `FailedScheduling` | No schedulable node |

## Things not to do

- **Do not** call `use_kubectl` for China-region EKS. Ever.
- **Do not** add a new MCP server for kubectl access — `call_kubectl` already
  lives inside the existing `aws-cn-2` connection.
- **Do not** use `call_aws` + CloudWatch as a kubectl substitute — `call_kubectl`
  gives direct Kubernetes API access and is more accurate.
- **Do not** issue write verbs via `call_kubectl` — they are blocked. Draft
  the remediation command and request human approval via the mitigation skill.

## Source & license

This open-source skill is cataloged on AgentStack and links to its original source — we do not rehost the code.

- **Author:** [aws-samples](https://github.com/aws-samples)
- **Source:** [aws-samples/sample-skills-for-AWS-Devops-agent](https://github.com/aws-samples/sample-skills-for-AWS-Devops-agent)
- **License:** MIT

Install and usage instructions live in the source repository linked above.

## Pricing

- **Free** — Free

## Security capabilities

Automated source analysis of v0.1.0 — what this tool can access:

- **Network access:** no
- **Filesystem access:** no
- **Shell / process execution:** no
- **Environment & secrets:** no
- **Dynamic code execution:** no

*"Yes" means the capability is present in the source — more access means more to trust, not that it is unsafe.*


## Versions

- **0.1.0** — security scan: passed — Imported from the upstream source.

## Links

- Listing page: https://agentstack.voostack.com/l/skill-aws-samples-sample-skills-for-aws-devops-agent-use-eks-via-call-kubectl
- Seller: https://agentstack.voostack.com/s/aws-samples
- Browse the marketplace: https://agentstack.voostack.com/browse

---
Listed on AgentStack — the marketplace for AI agent skills and MCP servers. Every listing is security-reviewed. Creators keep 70%.