// STRYKE-K8S — ENGINEERING REPORT

Opt-in stryke connector package · helper binary stryke-k8s-helper (publish=false) · CLI launcher k8s · NDJSON-over-pipe protocol

>_EXECUTIVE SUMMARY

stryke-k8s is one of the 14 opt-in connector packages in the stryke ecosystem. Kubernetes client for stryke. Get / apply / delete / scale / logs / watch / exec against any kubeconfig-reachable cluster (kind, k3s, minikube, EKS, GKE, AKS, OpenShift, vanilla). Opt-in package, statically linked.

Built on the kube crate (kube-client + kube-runtime). Drop-in replacement for kubectl one-liners that pipe through jq / yq / awk.

k8s
CLI launcher
opt-in
Tier
NDJSON
Helper protocol
14
Sibling stryke-* packages

~ARCHITECTURE

Two-process design: the stryke side is a thin .stk library that pipes calls to a sidecar helper. The helper is a regular Rust binary with the connector's full dependency tree; stryke core never links against it.

LayerImplementation
stryke library (lib/*.stk)Thin wrapper exposing typed functions; serializes args to NDJSON, deserializes responses
Helper binary (stryke-k8s-helper)Rust async (tokio); reads NDJSON from stdin, dispatches, writes NDJSON to stdout
Process modelOne helper subprocess per stryke session; lives as long as the stryke runtime needs it
BuildCargo with publish = false on the helper crate; the package itself ships via s pkg install -g .
Install path~/.stryke/bin/k8s after make install; PATH-resolvable from any shell
Testszunit-style under t/ with live-service variants when applicable
CIGitHub Actions .github/workflows/ci.yml — cargo fmt + clippy + test, plus stryke pkg install verification

$WHY OPT-IN (NOT BUILTIN)

Built on the kube crate (kube-client + kube-runtime). Drop-in replacement for kubectl one-liners that pipe through jq / yq / awk.

The trade-off is intentional. The core stryke binary stays under ~40 MB precisely because each connector ships separately. Daily-driver work (one-liners, awk replacement, data scripting) doesn't need MongoDB drivers, AWS SDKs, or Spark Connect bindings linked in.


&HELPER PROTOCOL

NDJSON over stdin/stdout. Each request line is a JSON object with an op field plus op-specific args. Each response is a JSON object on stdout (one per line). Errors are JSON objects with an error field plus a human-readable message.

# manual invocation (debugging)
echo '{"op":"version"}' | stryke-k8s-helper

# typical request shape
{"op":"", "...": ...}

# typical response shape
{"ok": true, "result": ...}
{"error": "...", "code": "..."}

/SCOPE

See the README's "Why this is a package" + "CLI: k8s" sections for the authoritative scope. The package is intentionally narrower than its underlying SDK / driver — the goal is "useful from a shell pipeline", not "complete API coverage".


#PROJECT METADATA

ItemValue
LicenseMIT
AuthorMenkeTechnologies
Repositorygithub.com/MenkeTechnologies/stryke-k8s
Parent languagestrykelang
Meta umbrellaMenkeTechnologiesMeta
Issuesgithub.com/MenkeTechnologies/stryke-k8s/issues