One thing to watch for with pod antiAffinity - if you use required vs preferred, and your pod count exceeds the node count, the remainder will be left in Pending and won't spin up anywhere.

There's a new feature which does a better job of spreading Pods without blocking scheduling quite as badly: https://kubernetes.io/docs/concepts/workloads/pods/pod-topol...

Having driven with the Tesla touchscreen, I can tell you you don't need to use it much while driving. The dials in the steering wheel can adjust the temperature, voice control is great for navigation and for selecting music, and range, performance data is on the dashboard (for non model 3).

If you need to do something complex like select a destionarion on the map, I don't think there's any interface that would let you do that safely as you need to visually identify a location.

I have a car with voice control and it's terrible for navigation with my 4 year old in the back seat. Seems it can't understand the phrase, "Drive to home why are you saying that daddy what did you say are you talking to the car daddy why?"

You can adjust the temperature from the scroll wheels on the steering wheel.

Isn't that the point? What a strange title for an article.

I thought the same. The title portraits the change as a negative thing and in the text there is no mention of the benefits that this brings :/

Very interesting - I've been working on exactly the same approach for a yum repo, but hadn't solved the race condition issue yet. I might have to "be inspired" by this post :)

If you want to run services in docker containers with Docker Toolbox (e.g. a mysql db), and you want the db stored on the Mac host, then you have to worry about 2 layers of folder mounts (one from host -> vm, one from vm -> container), another 2 layers of port forwarding (same as above), to make it 'feel' like your're running mysql locally.

With the beta, all of that is taken care for you with a couple of settings, and it's just much simpler to get up and running.

Even boot2docker (docker machines predecessor) could do that. It shared the folders correctly and managed port forwarding. Of course localhost stop working but I just added the ip in /etc/hosts and enter docker.local instead (the docks say the IP might change but that's never happened to me).

> It shared the folders correctly

Except on Mac, where it sometimes doesn't. Have you not run into permissions issues? Or having a file-watcher process running in the container not being triggered by changes from the host? There are a tonne of quirks that came with boot2docker. It was worth it, of course, but they were still there; and this app is specifically aiming to address them.

That's still the case with docker for Mac. Swapping xhyve for virtualbox doesn't eliminate the port forwarding or device mounting.

Docker For Mac also does some other cool things, for instance exposed container ports are available at the address `docker.local`. Solutions to help deal with filesystem permission mis-matches, filesystem notifications, and VPN compatibility (all of which are things VirtualBox struggles with) are also being baked in.

It does in the latest update. Just run "pinata set native/port-forwarding true" and your docker containers will be accessible via localhost. Previously this only worked with the VPN compatibility mode, but it's available on its own now.

I also recommend running "pinata set network nat".

There are still some rough edges, crashes when you resume from sleep (fixed in the latest update I might add), things like that. It's pretty close to an open beta in my opinion.