jsabo
Joined 14 years ago
Joined 14 years ago
Custom resources had/have some growing pains but I think worked out pretty well. It can be very very hard to test and distribute them though. As someone who maintained a controller with paid support, your test matrix gets pretty large pretty fast accounting for different k8s versions, different hosted versions (GKE, AKS, etc), different distros (openshift, rancher, etc). And that's before you even get into specific configurations like pod security policies, can the control plane communicate with the data plane, is there a service mesh.
Resource versioning is hard to get right. Once a resource type is v1, it becomes difficult to extend it. You can't add a beta field to it easily. Revising schema can be hard since anything more than a no op conversion between versions requires a webhook, which requires a certificate chain, and while cert-manager is popular it is not ubiquitous and regularly has breaking changes. Webhook setup issues made up a large portion of our support requests.
As far as the general "reconciliation loop" architecture goes, you end up with something similar in most orchestration systems I've worked on, or you wish that you did. So overall I think that worked out well. Getting it right can be hard, but I think that's the nature of the beast.
Oracle, which develops VirtualBox, said in an emailed statement that the company was "aware" of the problem, and fixed the code, adding that it will release a maintenance update soon.
"We will release a VirtualBox 4.3 maintenance release very soon. Apart from this, only a limited amount of users should be affected as the floppy device emulation is disabled for most of the standard virtual machine configurations," said software lead Frank Mehnert.
This line from the article was a little silly: "In the end, the secret was to precisely control the temperature both in the smoker and in the meat over the “low and slow” smoke."
When really the importance of heat control is pretty well known. Something I use and that may be of interest to HN is a heatermeter:
https://github.com/CapnBry/HeaterMeter
which uses a fan to maintain a set temperature automatically and has a web interface to monitor it remotely. The article mentioned the students had built something similar too.
Apparently during congressional testimony they mentioned that venues, and sometimes artists or promoters, get a cut of the service fee. They quote some mid-level promoters that dispute the promoter/artist fee but it doesn't really go into the venue statement. In my experience with small shows, the venue's money is baked into the ticket price, not the additional fees.
https://www.kut.org/austin/2020-03-18/judge-throws-out-city-...
Though granted this law was passed previously and wasn't a reaction to something Austin did a la TNC regulation