Inspecting an application kcp

The long form of the README inspection section: the helpers, every state path, the embedded k3s and the ssh access. Short path in the README.

A production application has its own kcp; the applications of a market network share the network's kcp, one workspace each (root:<app>). A kcp admin kubeconfig's server URL ends in /clusters/<workspace>; swap the workspace to walk the kcp. Define two helpers:

kc() { local k=$1 ws=$2; shift 2; local b; b=$(kubectl --kubeconfig $k config view -o jsonpath='{.clusters[0].cluster.server}' | sed 's#/clusters/.*##'); kubectl --kubeconfig $k --server "$b/clusters/$ws" "$@"; }
tree() { local k=$1 ws=${2:-root}; echo "$ws"; for c in $(kc $k $ws get workspaces -o name 2>/dev/null | sed 's#.*/##'); do tree $k "$ws:$c"; done; }

Find every kcp and every tenant cluster kubeconfig under a state root:

STATE=${XDG_STATE_HOME:-$HOME/.local/state}/socialweb-computer/dev/<instance>   # a dev instance
find $STATE /var/lib/socialweb-computer -name admin.kubeconfig -path '*kcp/admin.kubeconfig'   # every kcp front kubeconfig
find $STATE /var/lib/socialweb-computer -path '*server/cred/admin.kubeconfig'                   # every tenant k3s kubeconfig
for K in $(find $STATE -path '*kcp/admin.kubeconfig' -not -path '*slot-*' -not -path '*shared*'); do echo "== $K"; tree $K; done
kc $K root api-resources --api-group=socialweb.computer    # the kinds this layer serves

• dev env prints the network's kcp kubeconfig and ports.
• A child application of a market network has no kcp of its own: walk root:<app> of the network's kcp. Its state (component state dirs, its OpenBao) is under the network's state dir, in apps/.
• A production bidder's kcp is under /var/lib/socialweb-computer/swc-bidder/handles/<hash>/kcp, and a production gateway's kcp is under its state dir (default /var/lib/socialweb-computer/socialweb/kcp). A claim lives in the cluster's workspace: kc $K root:<acct>:<cluster> get nodeclaims.
• A production host has no kubectl; use the gateway's embedded k3s: K3S=$(find /var/lib/socialweb-computer/socialweb/runtime -name k3s -type f | head -1); $K3S kubectl ....

Every component runs in the socialweb-computer core process, so component logs are the core's: journalctl --user -u <unit>, or dev logs core for a dev instance. A dev restart <instance> <component> restarts one component through its kcp object.

SSH to a production host: ssh -i ~/.ssh/id_ed25519_no_password -p 1997 root@socialweb.computer.

License

Unlicense (public domain).

See also

• ARCHITECTURE