What we run
Machines, not adjectives.
Packet Analysis is the lead. When the fault is the platform, the second machine is K3 / Kubernetes platform migration on demand — the RILEY Dashboard, already shipping. By Design is how a change proves itself before merge.
01 · Lead
Packet Analysis
What we run
Wireshark and tcpdump on the path. Kubeshark on in-cluster API and service traffic. eBPF on the Kubernetes stack: Cilium, Hubble, bpftrace, BCC, custom kprobes and tracepoints, socket filters, cgroup v2 watermarks. NetFlow and SNMP when flow and fabric fill the gap.
What you get
Cause across service · network · compute, sized to a fix. Not a PCAP left on a laptop, and not a dashboard that stopped at the symptom. Pedigree: 25+ years of national TELCO packet forensics.
02 · Shipped
K3 platform migration on demand
What we run
The RILEY Dashboard is the pane of glass for a Kubernetes fleet moving onto KRO. RileyApplication is the source of truth. Argo is the sync engine under that definition, not a pile of hand-written application YAML. Conductor is deprecated; orchestration moves to Temporal.
What you get
A runway in priority order. The Apps board is one row per product: health, containers, pods, restarts, cluster, namespace, and whether it is managed from the KRO source of truth or from legacy sync. Still-broken is not the same as open. A row opens its containers, then Start workspace runs the change and stops at a pull request.
The console below is a sanitized demonstration of that operating picture. Six fictional applications. No live cluster, no secrets, no internal host.
RILEY Dashboard
K3 / Kubernetes platform migration on demand.
One row per product. Health, restarts, and where the app is managed from — KRO source of truth or legacy sync — with priority on the left. Click a product to open its containers. This board is a demonstration, not a live cluster.
| Containers | Pods R/P/F | Cluster | Namespace | Managed from | Issues | ||||
|---|---|---|---|---|---|---|---|---|---|
| P0 | Degraded | 4 | 1/0/2 | 26 active 18m | edge | ingress | Legacy sync | 1 | |
| gateway | Degraded | 22 | container · session-gateway | ||||||
| proxy | Healthy | 4 | container · session-gateway | ||||||
| P1 | Degraded | 6 | 3/1/1 | 11 settling 2h | apps | runtime | KRO SSOT | 1 | |
| P1 | Unknown | 2 | 0/0/0 | 0 — | edge | ingress | Legacy sync | 0 | |
| P1 | Progressing | 3 | 2/1/0 | 7 stable 1d | core | data | Legacy sync | 1 | |
| P2 | N/A | 0 | 0/0/0 | 0 — | core | observe | KRO SSOT | 0 | |
| P2 | Healthy | 1 | 1/0/0 | 3 stable 9d | apps | runtime | KRO SSOT | 0 | |
| P2 | Healthy | 2 | 2/0/0 | 4 stable 9d | core | policy | KRO SSOT | 0 | |
| P2 | Healthy | 5 | 5/0/0 | 44 stable 9d | apps | runtime | KRO SSOT | 1 | |
The issue was closed. The same drift came back on the next collect.
03 · Gate
riley-pr-check and bverify
What we run
By-Design checks in CI. The 9-Layer Verification Engine dynamically selects what the diff needs, from physical through cognitive governance. The 4-Round Quadriad is R1 Expected-Red on main, R2 Expected-Green on the pull request, R3 zero-leak / 0→1→0, R4 sabotage caught.
What you get
A gate that fails closed. The agent that picked the tests does not edit them, mute them, or rewrite the raw result. It summarizes. Proof trail: revive_labs #932 and #959. Run it on bare metal, Docker, Kubernetes, and Cloud MicroVMs.
04 · Watch
Remote monitoring, sized to the application
What we run
Remote probes, log intelligence, and a health / reaper path customized to how your service actually runs. revive_labs #956.
What you get
A picture of launcher, serve, and Cloud that operators can act on. Closed-loop reaping for leaked PTYs and zombie trees, tied back to the True SRE ladder when the wire has to be read.
05 · Loop
Performance and benchmarking
What we run
A performance loop across any service or application: measure, diagnose on Service → Network → Compute, change config or code or architecture, re-measure. Agentic Development Workflows keep that loop repeatable.
What you get
The loop proved on bare metal between Calgary and Montreal, then extended to any cloud or enterprise network. No invented savings on this site.