Readit NewsUpdate: https://gizmodo.com/republicans-project-2025-would-end-free-...
yuck
In step 1, the register uses the source path 'github-events' but the payload is using 'github-pushes'.
In step 3 it says filter_query passes since payload->>'ref' is 'refs/heads/main' but we never see that filter being inserted in the service, the only filter we see is type IN (\'PushEvent\', \'PullRequestEvent\').
Was the article edited midway through and missed some pieces?
That's your problem right there. You really don't want to be setting up and managing a cluster from scratch for anything less than a datacenter-scale operation. If you are already on a cloud provider just use their managed Kubernetes offering instead. It will come with a free control plane and abstract away most of the painful parts for you (like etcd, networking, load balancing, ACLs, node provisioning, kubelets, proxies). That way you just bring your own nodes/VMs and can still enjoy the deployment standardization and other powerful features without the operational burden.
[1] https://varnish-cache.org/docs/trunk/phk/h2againagainagain.h...
The ability to build a single static binary that works on Linux, Mac and Windows using Go would be life changing for the internal tools I develop at work.