// Show the gateway for a network interface in a Kubernetes pod. Reads the routing table via `ip -j route` from the pod's network namespace. First resolve_pod_netns, then node_script with netns param.
| name | pod-show-gateway |
| description | Show the gateway for a network interface in a Kubernetes pod. Reads the routing table via `ip -j route` from the pod's network namespace. First resolve_pod_netns, then node_script with netns param. |
This skill runs in the pod's network namespace using host tools. Two steps required:
resolve_pod_netns: pod="<pod>", namespace="<ns>"
node_script: node="<node>", netns="<netns>", skill="pod-show-gateway", script="show-gateway.sh", args="<args>"
| Parameter | Required | Description |
|---|---|---|
--interface IFACE | no | Network interface name. If omitted, shows all. |
--json | no | Output in JSON format |
resolve_pod_netns: pod="rdma-pod", namespace="rdma-test"
→ node="worker-1", netns="abc123"
node_script: node="worker-1", netns="abc123", skill="pod-show-gateway", script="show-gateway.sh", args="--interface net1"
node_script: node="worker-1", netns="abc123", skill="pod-show-gateway", script="show-gateway.sh"
node_script: node="worker-1", netns="abc123", skill="pod-show-gateway", script="show-gateway.sh", args="--json"
The output table includes a TYPE column identifying each interface type:
| TYPE | Meaning |
|---|---|
RoCE | Ethernet interface with an RDMA device attached |
Ethernet | Regular Ethernet interface |
IB | InfiniBand interface |
Detection logic: /sys/class/net/<dev>/type = 32 → IB; type=1 and rdma link contains netdev <dev> → RoCE; otherwise → Ethernet.
JSON output (--json) also includes a type field in each gateway entry.
See node-show-gateway for the node version.
Guide for writing and improving Siclaw skills. Read this when creating or modifying a skill. Covers SKILL.md format, script execution modes, and best practices.
Check node health and diagnose node-level issues (NotReady, DiskPressure, MemoryPressure, PIDPressure). Inspects node conditions, resource allocation, and real-time usage.
Diagnose DNS resolution failures in the cluster (NXDOMAIN, timeouts, SERVFAIL). Checks CoreDNS health, service endpoints, and DNS configuration.
Ping a pod's gateway for a given network interface. Auto-detects gateway IP from the routing table, then pings it. First resolve_pod_netns, then node_script with netns param.
Retrieve logs from a Kubernetes node. Supports journalctl (systemd units) and file-based logs. Use when you need to inspect node-level logs (containerd, kubelet, etc.). Execute via node_script tool.
Diagnose NetworkPolicy-related connectivity issues (traffic unexpectedly blocked, default-deny effects, egress blocking DNS). Identifies which NetworkPolicies affect a pod, checks ingress/egress rules, and verifies CNI support.