> so wouldn't you accomplish HA without the pseudocontroller by just putting both pods in the Service?
I'm not sure how fast that would be, the extra controller container is needed for the almost instant failover.
Answering your second question, why not an init container in the secondary, because now we can scale that failover controller up over multiple nodes, if the node where the (fairly stateless) controller runs goes down, we'd still have to wait until k8s schedules another pod instead of almost instantly.
Would they work as performant and use the same amount of (less, almost nothing) resources? I've ran mosquito clusters with tens of thousands of connected clients, thousands of messages per second, on 2 cores and 2GB of ram, while mostly idling. (Without retention, using clean sessions and only QoS 0)...
Using the VoIP credentials of my ISP in the Fritz!Box or ATA and nothing else. (which they must provide since The Netherlands has free modem choice: https://web.archive.org/web/20230921231725/https://www.acm.n...), no other setup involved, no port forwarding, etc.
Try Pidgin with the excellent ms teams plugin: https://github.com/EionRobb/purple-teams - less than 100mb ram usage and notifications that still work after an hour. Only for (video) calls you need to open teams..
esphome is by far the best and most useful piece of software I've encountered in a long time!
Even for non home automation. Simple web API to turn gpio's on or off, coupled with some relays makes for a great easy yaml configurable industrial automation system
I completely agree, using ESPHome beats writing firmware from scratch, even though lots of Arduino libraries are available. But the flip side is that ESPHome is in active development with lots of contributors, so sometimes things don't work as you might expect. And if that happens, your only option is to spin up an IDE and dive into source code :) For example, during this project I had to fork an abandoned OpenTherm library and rewrite almost half of it, as well as contribute a couple of bugfixes to ESPHome itself. It was actually fun, and I expected something like that from the beginning, but such a sharp drop from a cliff when YAML config doesn't work, will be a surprise for most people :)
I'm not sure how fast that would be, the extra controller container is needed for the almost instant failover.
Answering your second question, why not an init container in the secondary, because now we can scale that failover controller up over multiple nodes, if the node where the (fairly stateless) controller runs goes down, we'd still have to wait until k8s schedules another pod instead of almost instantly.