u/ChaseApp501

It was fun watching him get eviscerated on twitter

kubernetes

RIP Eliana Moreno

appreciate that

Why not NATS JetStream? It is insanely fast, easy to use/setup, 11mb~ binary, you can run a cluster + leaf nodes, etc. You also get Object Storage and KV for free.

ServiceRadar can monitor your network, works great especially if you have a router that can send syslog, netflow, etc like a Ubiquiti Dream Pro. You can install the serviceradar-agent on your VMs/hypervisor/hosts/workstations for even more visibility.

ServiceRadar is opensource and free, you can self-host everything in docker containers or kubernetes, and does pretty much everything PRTG can. There is also a cloud version that we are rolling out soon if you're interested in a pilot, let me know. https://serviceradar.cloud/

We are looking for help on a custom PCB design for a WiFi survey tool if you're interested, drop me a line. All outputs/build artifacts will be open-source.

Couldn't upload the video or any screenshots, sorry about that. https://www.tiktok.com/@mfreeman451/video/7675557229642157326

https://serviceradar.cloud/blog/building-fieldsurvey blog is up

I don't have a new Android phone yet so can't really help you there, sorry.. Would love to see this get ported though.

Not GPS. The iPhone runs ARKit world tracking (camera + IMU, LiDAR on Pro models) and RoomPlan from the same session. That gives a 6DOF pose in the survey’s local coordinate frame, and we attach each Sidekick RF observation to that pose. So the map is "where I am in this walk," not WGS84.

HackRF One is about 20 MHz wide at any instant, which is already a full 20 MHz channel. 80/160 MHz 5 GHz is wider than one look, so 'hackrf_sweep' retunes across the band and dumps FFT power bins (we use 1 MHz bins). The Sidekick folds those onto channel centers and scores energy, this is a separate stream from the USB monitor-mode dongles, which are what decode beacons / BSSID / RSSI.

It adds energy that is not a decodeable AP: microwave, analog video, radar, adjacent-channel splat, something quiet the hopper has not sat on yet and this is what you see as the spectrum bar on the phone and the interference overlay later.

I had to look that up, sounds like a good idea

I don't want to nitpick your post but can't help myself, I think there are better choices than nginx -- traefik, or envoy gateway. Besides all of the confusion around the CNCF (EOL) version vs. F5, running anything from nginx gives me major anxiety around security.

I learned kubernetes with a lot of help from AI and have been running it at home, and at work 3~ years now. I run k3s in multiple clusters and got going with a couple of servers off of ebay, I spent about 500-700$ on 48 core servers with lots of RAM (DDR3, nothing special).

Each server gets loaded up with ProxMox, from there I carve out 4 VMs on each server - 1 for the k3s control plane, and 3 worker nodes. I also setup additional LXCs on each proxmox PVE for etcd (you'll cluster the 3 etcd nodes https://docs.k3s.io/datastore/ha). They're probably a bit more now since AI driving the prices of everything up, but 2 or 3 servers and you are good to go.

I settled on k3s and Calico. I also have a Ubiquiti based network and UDM Dream Pro router. I got a free IPv6 tunnel from tunnelbroker.net, did my IPv6 certification with them (free and you get a t-shirt), and terminated the tunnel on the UDM. This gives me plenty of IPv6 addressing at home to play -- you setup BGP on the router and peer with Calico in k8s. k3sup is a great tool for setting up k3s on each of the nodes, the control plane and the worker nodes will get different flags so just figure those out. You'll also probably want to make it so that your workloads don't get scheduled on any of the control planes, AI can help you through all of that as well.

The main reason or maybe the only reason to do this is so that you can have IP addresses for load balancers (metallb). Without this you're setting up nodeports and static routes all of the time and it's a lot more manual work. For authentication I've got Authentik IDP running in my cluster and a bunch of other stuff. This has been a journey for me that has been very rewarding and a great learning experience.

You will spend a lot of time on this before you feel comfortable with any of it, just work through the issues and keep going. I started with a really basic k3s setup and then ended up rebuilding several times before I landed on the configuration I gave you, start with whatever you're comfortable with.

Some other tools/software that I like:

k3s, falco, trivy, kubepromstack (grafana+prometheus), envoy gateway, cert-manager, externaldns (works great with cloudflare), argocd, cnpg (cloud-native postgres), longhorn, openbao, sealed-secrets, docker mailserver (DMS)

If you have GPUs in your cluster:

jupyterhub, nvidia-container-runtime

ServiceNow is an ITSM platform, we are doing network operations management, security analytics, and ITOM (IT Operations Management). It would take a long time to enumerate all of the things we've leveraged in the Elixir and the BEAM ecosystem that have given us a huge advantage.. ERTS/OTP is amazing and have allowed us to build distributed apps that are cloud-native and run nicely on kubernetes, we're really glad we didn't have to take that on ourselves.

We approached plugins a little bit differently -- we deploy a golang-based agent in the "edge" that runs WASM plugins through the wazero WASI runtime and that works really well for us.

We also have our own "dynamic UI" with our Dashboard SDK. You can build signed browser-module dashboards and then import, verify, and render. You own the dashboard, the app owns the datalayer. The developer experience is pretty simple, you just download the SDK and install the NPM CLI, generate the scaffolding/template, design your dashboard, run/test/iterate locally completely outside of ServiceRadar, and then publish with the NPM CLI when you're done.

https://developer.serviceradar.cloud/docs/v2/dashboard-sdk

Our biggest challenge was the build system to be honest. We have a large monorepo where we build containers and packages for services written in Elixir, Golang, Rust, Swift, C (BPF), etc. We are using bazel for this now and it has been a bit of a rocky road since the elixir rules were abandonded years ago and were never good to begin with, but as of a few days ago and a lot of hard work from one of our lead developers, those have been revived and are actually really good for the first time ever.

Just to be clear, the CRM I mentioned originally is not part of this network operations management platform, we wrote it separately to help us sell the SaaS kinda thing.

https://github.com/bazelverse/rules_elixir

https://github.com/carverauto/serviceradar

https://serviceradar.cloud/