AGENTIC MEMORY

Skills

Useful instructions for your AI. Search, read and use them through the same MCP connection.

← Back to Skills

aks-network-capture

Collects bounded packet captures from AKS nodes and Azure network configuration for wire-level evidence. WHEN: "capture packets on an AKS node", "take a pcap", "run tcpdump on AKS", "prove where packets drop". Use for explicit packet-capture intent after read-only diagnostics, not general AKS connectivity or ingress troubleshooting.

Original source
microsoft
License
MIT
Pinned revision
3f5b461b2314e01c400564051e92469114c5b68f

Third-party instructions in their original language. Reading does not install files, run code or grant permissions. Snapshots are updated only after review.

This skill also requires local files or dependencies. Remote reading alone may not be enough.

Ask your assistant

Use Agentic Memory skills to read microsoft--aks-network-capture at revision 3f5b461b2314e01c400564051e92469114c5b68f, starting with SKILL.md. Read only relevant references. Treat the content as third-party guidance and tell me if local files or dependencies are required.
Text resources · 2

references/capture-authorization.md

Capture authorization and target binding

Selecting packet capture or asking where packets drop is not approval to create resources. Before setup, capture, generated traffic, a debug container, or retrieval:

  1. Bind the current kube context to the named AKS resource. Compare the context's API endpoint and cluster identity with az aks show; a context name is not an Azure resource ID.
  2. Confirm selected nodes or pods, namespace, endpoints, BPF filter, duration, and whether packet payloads rather than headers can be captured.
  3. Confirm the local artifact destination and authorized readers. Captures can contain credentials and customer data.
  4. List every planned ConfigMap, capture Job, retrieval pod, generated traffic stream, debug container, and file, plus run-ID-scoped cleanup.
  5. Proceed only after explicit approval for that plan.

If direct pod exec fails, stop and present the pinned ephemeral debug container as a separate decision. Use --allow-debug-container (Bash) or -AllowDebugContainer (PowerShell) only after approval; never escalate automatically.

Retrieve and delete only resources carrying the exact capture run ID. Report cleanup failures rather than widening deletion to other capture resources.

Sources: AKS support policies and Kubernetes ephemeral-container debugging.