Static IP addresses and routing priority configured across physical LAN, WireGuard cloud tunnel, and Tailscale peer mesh:
| DEVICE NAME | HOSTNAME | USER | LAN IP | WIREGUARD | TAILSCALE | INGRESS / ROLE |
|---|---|---|---|---|---|---|
| MacBook Air | das-MacBook-Air.local | da | 192.168.4.141 | — | 100.71.196.91 | Primary Workstation (Apple Silicon M1, 16GB RAM) |
| MacBook Pro | Doxs-MacBook-Pro.local | dx | 192.168.4.175 | — | 100.102.41.17 | Secondary Workstation (Intel i9, 32GB RAM, Password: jawlan) |
| x1 (Master) | xrpi1 | x1 | 192.168.4.139 | 10.10.0.2 | 100.95.125.43 | Primary Cluster Master, NVMe Storage, K3s API (6443) |
| x2 (Worker) | xrpi2 | x2 | 192.168.4.146 | 10.10.0.3 | 100.71.97.80 | K3s Edge Worker, HDMI Kiosk Surface, VNC (5900) |
| AWS Hub (EC2) | ip-172-31-2-180 | ubuntu | — | 10.10.0.1 | — | 54.215.48.95 (Nginx Reverse Proxy & SSL Termination) |
| dphone | dphone | — | — | — | 100.64.94.78 | Operator Mobile iOS Client (Tailscale Mesh) |
Dedicated ChaCha20-Poly1305 kernel-level encrypted tunnel connecting the AWS Ingress gateway directly to on-premise nodes x1 (10.10.0.2) and x2 (10.10.0.3).
Global peer-to-peer mesh linking mobile client (dphone), MacBook Air, MacBook Pro, and edge cluster nodes across any NAT without port forwarding.
Gigabit on-premise Ethernet and 5GHz Wi-Fi backplane connecting workstations and micro-servers with sub-millisecond round-trip latencies.
Unified Namespace (UNS) architecture mapping industrial field protocols to Sparkplug B MQTT topics and enterprise time-series historians:
| NODE | OPERATING SYSTEM | ARCH | PROCESSOR | RAM | PRIMARY STORAGE |
|---|---|---|---|---|---|
| MacBook Air | macOS 26.5.2 (Darwin 25) | arm64 | Apple M1 (8 cores) | 16 GB Unified | 500 GB NVMe APFS |
| MacBook Pro | macOS 26.7 (Darwin 25) | x86_64 | Intel Core i9-9880H (8C/16T) | 32 GB DDR4 | 1.1 TB NVMe APFS |
| x1 (Master) | Debian 13 (Trixie) | aarch64 | Broadcom BCM2712 (4 cores) | 8 GB LPDDR4X | 500 GB NVMe PCIe Gen3 |
| x2 (Worker) | Debian 13 (Trixie) | aarch64 | Broadcom BCM2711 (4 cores) | 8 GB LPDDR4 | 64 GB MicroSD |
| AWS Hub | Ubuntu 24.04 LTS | x86_64 | AWS Nitro vCPU | 1 GB Burst | 30 GB gp3 EBS |
Modern autonomous edge deployments require strict architectural separation between stateful persistence and stateless ingress execution. In this topology, CORE-MASTER-01 (x1) anchors the dedicated high-IOPS persistent storage tier, isolating write-intensive transactional databases, InfluxDB write-ahead logs (WAL), RabbitMQ durable queues, and enterprise SCADA transaction groups into dedicated volume enclaves.
EDGE-GATEWAY-02 (x2) operates under a strictly enforced stateless paradigm. High-frequency industrial telemetry, edge ingress routing, and visualization pipelines run completely decoupled from local persistent state. By policy-constraining all StatefulSets to the master storage enclave via Kubernetes nodeAffinity, the edge worker executes purely in-memory workloads (Traefik ingress routing, OT protocol translation, and high-framerate kiosk rendering).