I won't say REST is perfect, but I much prefer it to an unstructured api where anything goes. You didn't suggest that, but you really didn't suggest any alternative.
What's the alternative to relying on documentation? Is relying on documentation even a bad thing?
There's been a surge in discussion of online cheating in poker. some online poker players certainly use real time assistance. There's also bots grinding online too.
The prevalence is an open question, though. I imagine it's rather high since there's a huge incentive to cheat.
There might be some issues with web sockets over a cellular connection. I'm no expert, but I've read that historically there are issues there. This might not be the case anymore though.
It may be easy to cycle hosts in and out, but it can also be time consuming, apparently. In the article it mentions taking 45 days to patch all hosts. The article also points out that this is too long for security updates.
Nothing will work 100% of the time. If their patching mechanism is thoroughly tested and battle hardened, I think the risk would be acceptable. Once you do the initial kpatch security upgrade, you could even schedule the machine for serivce so that it's not relying on that, limiting your exposure to bugs.
Kind of like replacing a portion of unoptimized compiler code with hand written assembly?