Things like this are literally just so that there is a test case to make it up to the Supreme Court. They do something ridiculous that obviously violates the intent of the law but mostly stays inside the letter of the law, in hopes that the Supreme Court will take it up and overturn the law. So, yes, the fact that the vending machine can technically sell bullets to minors is a feature, not a bug. Why is their endgame getting rid of age restrictions for firearms and ammunition? You’d have to ask the death cult themselves about that one.

There is a lot of complexity and overhead involved in either system. But, the benefits of containerizing and using Kubernetes allow you to standardize a lot of other things with your applications. With Kubernetes, you can standardize your central logging, network monitoring, and much more. And from the developers perspective, they usually don’t even want to deal with VMs. You can run something Docker Desktop or Rancher Desktop on the developer system and that allows them to dev against a real, compliant k8s distro. Kubernetes is also explicitly declarative, something that OpenStack was having trouble being.

So there are two swim lanes, as I see it: places that need to use VMs because they are using commercial software, which may or may not explicitly support OpenStack, and companies trying to support developers in which case the developers probably want a system that affords a faster path to production while meeting compliance requirements. OpenStack offered a path towards that later case, but Kubernetes came in and created an even better path.

PS: I didn’t really answer your question”capable” question though. Technically, you can run a kubernetes cluster on top of OpenStack, so by definition Kubernetes offers a subset of the capabilities of OpenStack. But, it encapsulates the best subset for deploying and managing modern applications. Go look at some demos of ArgoCD, for example. Go look at Cilium and Tetragon for network and workload monitoring. Look at what Grafana and Loki are doing for logging/monitoring/instrumentation.

Because OpenStack lets you deploy nearly anything (and believe me, I was slinging OVAs for anything back in the day) you will never get to that level of standardization of workloads that allows you to do those kind of things. By limiting what the platform can do, you can build really robust tooling around the things you need to do.

I used to be a certified OpenStack Administrator and I’ll say that K8s has eaten its lunch in many companies and in mindshare.

But if you do it, look at triple-o instead of installing from docs.

I think it’s worth saying that the head unit failing in this scenario is very disruptive for two reasons:

First and foremost, the purpose of this journey in this car is to review the car. So if the head unit craps out, and he doesn’t make every effort to reboot it, and he mentions it in the review, he loses a lot of credibility from the users and industry folks. Could you imagine a review for a computer where it crashes or turns off, and the reviewer just says “welp, that’s all folks”?

My second point is that he is navigating in an unfamiliar place to a charger for the car. If you’re coming from Tesla or AA/CarPlay, this is something you expect to work flawlessly. And it’s part of the review that’s worth discussing whether or not it works.

In my opinion, even if he 100% knew where he was going, his behaviors are justified for a review.

Good to hear they have that covered already. Looks like a great tool!

But I could take ‘flower.jpg’, which is an actual flower, and embed a second image, ‘csam.png’ inside it. Your scanner would scan ‘flower.jpg’, find it to be acceptable, then in turn register ‘csam.png’. Not saying that this isn’t a great start, but this is the reason that a lot of websites that allow uploads re-encode images.

The fun part is that it’s still a valid JPEG file if you put more data in it. The file should be fully re-encoded to be sure.