How do I install the Fakoli Nat464 Sidecar K8S Sidecar Testing skill?

Run npx skillmds@latest add tomevault-io/fakoli-nat464-sidecar-k8s-sidecar-testing in your terminal (requires Node.js), paste this page's agent-chat prompt into Claude, Cursor, or any MCP-connected agent, or download the SKILL.md file and copy it into your agent's skills directory.

What does the Fakoli Nat464 Sidecar K8S Sidecar Testing skill do?

K8s Sidecar Testing It is listed under DevOps & Infra on SkillMD.

Is Fakoli Nat464 Sidecar K8S Sidecar Testing safe to use?

This skill has not completed SkillMD's automated safety review yet. Independent scanners report: SkillSpector: PASS, Skill Scanner: PASS. SkillMD never runs a skill's scripts for you; review the SKILL.md before installing.

Which AI agents work with Fakoli Nat464 Sidecar K8S Sidecar Testing?

This skill is tagged as working with Claude Code, Claude.ai, OpenAI Codex. SKILL.md is an open format, so most agents that read a skills directory can load it too.

Is Fakoli Nat464 Sidecar K8S Sidecar Testing free to use?

Yes. Installing skills from SkillMD is free, and the skill stays under its author's original license.

Who published Fakoli Nat464 Sidecar K8S Sidecar Testing?

tomevault-io (@tomevault-io) published this skill. Their other Agent Skills are listed on their SkillMD profile.

Fakoli Nat464 Sidecar K8S Sidecar Testing by tomevault-io

Name: Fakoli Nat464 Sidecar K8S Sidecar Testing
Author: tomevault-io

File contents

K8s Sidecar Testing

Test nat464-sidecar in an IPv6-only Kubernetes cluster using Multipass VMs and k3s.

Workflow

Execute phases in order. Each phase has a corresponding script in scripts/.

Phase 1: VM Provisioning (run on Mac)

scripts/vm-setup.sh [vm-name] [cpus] [memory] [disk]
# Defaults: nat464-dev, 2 CPUs, 4G RAM, 20G disk

Then transfer the project into the VM:

tar czf /tmp/nat464.tar.gz -C /path/to nat464-sidecar
multipass transfer /tmp/nat464.tar.gz nat464-dev:/home/ubuntu/
multipass shell nat464-dev
# Inside VM:
tar xzf nat464.tar.gz

Phase 2: k3s Cluster Setup (run inside VM)

scripts/k3s-setup.sh

Creates an IPv6-only pod network emulating AWS EKS:

Pod CIDR: fd00:42::/56 (IPv6-only, like EKS)
Service CIDR: fd00:43::/112 (IPv6-only)
Node: dual-stack (like EKS ENI nodes)
CoreDNS DNS64 with 64:ff9b::/96 prefix

Phase 3: Build Container Image (run inside VM)

scripts/build-image.sh [project-dir]
# Default: /home/ubuntu/nat464-sidecar

Builds with Docker, imports into k3s containerd.

Phase 4: Deploy and Verify (run inside VM)

scripts/deploy-test.sh [manifest-path]
# Default: /home/ubuntu/nat464-sidecar/deploy/example-pod.yaml

Runs four automated tests:

Health check (/healthz endpoint)
Inbound translation (curl -6 pod:8080 through sidecar to nginx:80)
Sidecar logs inspection
Pod status verification

Manual outbound test:

kubectl exec nat464-demo -c app -- curl -x socks5h://127.0.0.1:1080 http://example.com

Phase 5: Benchmark (optional, run inside VM)

scripts/benchmark.sh

Measures baseline vs sidecar-translated throughput using iperf3.

Phase 6: Teardown

scripts/teardown.sh          # Clean pods/images, keep VM
scripts/teardown.sh --vm     # Also delete the Multipass VM

Quick Verification Commands

From inside the VM after deployment:

export KUBECONFIG=/etc/rancher/k3s/k3s.yaml
POD_IPV6=$(kubectl get pod nat464-demo -o jsonpath='{.status.podIPs[0].ip}')

# Health
kubectl exec nat464-demo -c app -- wget -qO- http://localhost:9464/healthz

# Inbound: IPv6 → IPv4
kubectl run curl-test --rm -i --restart=Never --image=curlimages/curl -- curl -6 -s http://[${POD_IPV6}]:8080/

# Outbound: IPv4 → IPv6 via SOCKS5
kubectl exec nat464-demo -c app -- curl -x socks5h://127.0.0.1:1080 http://example.com

# Logs
kubectl logs nat464-demo -c nat464-sidecar

Troubleshooting

See references/troubleshooting.md for common issues with VMs, k3s, pod networking, and IPv6 connectivity.

Converted and distributed by TomeVault — claim your Tome and manage your conversions.

---name: fakoli-nat464-sidecar-k8s-sidecar-testingdescription: K8s Sidecar Testing---# K8s Sidecar TestingTest nat464-sidecar in an IPv6-only Kubernetes cluster using Multipass VMs and k3s.## WorkflowExecute phases in order. Each phase has a corresponding script in `scripts/`.### Phase 1: VM Provisioning (run on Mac)```bashscripts/vm-setup.sh [vm-name] [cpus] [memory] [disk]# Defaults: nat464-dev, 2 CPUs, 4G RAM, 20G disk```Then transfer the project into the VM:```bashtar czf /tmp/nat464.tar.gz -C /path/to nat464-sidecarmultipass transfer /tmp/nat464.tar.gz nat464-dev:/home/ubuntu/multipass shell nat464-dev# Inside VM:tar xzf nat464.tar.gz```### Phase 2: k3s Cluster Setup (run inside VM)```bashscripts/k3s-setup.sh```Creates an IPv6-only pod network emulating AWS EKS:- Pod CIDR: `fd00:42::/56` (IPv6-only, like EKS)- Service CIDR: `fd00:43::/112` (IPv6-only)- Node: dual-stack (like EKS ENI nodes)- CoreDNS DNS64 with `64:ff9b::/96` prefix### Phase 3: Build Container Image (run inside VM)```bashscripts/build-image.sh [project-dir]# Default: /home/ubuntu/nat464-sidecar```Builds with Docker, imports into k3s containerd.### Phase 4: Deploy and Verify (run inside VM)```bashscripts/deploy-test.sh [manifest-path]# Default: /home/ubuntu/nat464-sidecar/deploy/example-pod.yaml```Runs four automated tests:1. Health check (`/healthz` endpoint)2. Inbound translation (curl -6 pod:8080 through sidecar to nginx:80)3. Sidecar logs inspection4. Pod status verificationManual outbound test:```bashkubectl exec nat464-demo -c app -- curl -x socks5h://127.0.0.1:1080 http://example.com```### Phase 5: Benchmark (optional, run inside VM)```bashscripts/benchmark.sh```Measures baseline vs sidecar-translated throughput using iperf3.### Phase 6: Teardown```bashscripts/teardown.sh # Clean pods/images, keep VMscripts/teardown.sh --vm # Also delete the Multipass VM```## Quick Verification CommandsFrom inside the VM after deployment:```bashexport KUBECONFIG=/etc/rancher/k3s/k3s.yamlPOD_IPV6=$(kubectl get pod nat464-demo -o jsonpath='{.status.podIPs[0].ip}')# Healthkubectl exec nat464-demo -c app -- wget -qO- http://localhost:9464/healthz# Inbound: IPv6 → IPv4kubectl run curl-test --rm -i --restart=Never --image=curlimages/curl -- curl -6 -s http://[${POD_IPV6}]:8080/# Outbound: IPv4 → IPv6 via SOCKS5kubectl exec nat464-demo -c app -- curl -x socks5h://127.0.0.1:1080 http://example.com# Logskubectl logs nat464-demo -c nat464-sidecar```## TroubleshootingSee [references/troubleshooting.md](references/troubleshooting.md) for common issues with VMs, k3s, pod networking, and IPv6 connectivity.---> Converted and distributed by [TomeVault](https://tomevault.io/claim/fakoli) — claim your Tome and manage your conversions.

Frequently asked questions

Fakoli Nat464 Sidecar K8S Sidecar Testing