[ntnn]

That sounds like a shoehorned explanation. You're leaving developers on linux out to dry because people aren't paying attention to their production systems?

Don't get me wrong, the work you guys do is cool and all, but that isn't a valid explanation from my point of view. Any company should have some sort of staging to test updated before rolling them out - it isn't up to the developers of the software to take care of this.

And not only that - the switch will come at some point or another either way, so it doesn't make sense to hold that back from CE on linux so that someone doesn't 'find an unexpected and unwanted kubernetes distribution wedged in'. Those who would find that now would also be surprised by that later on.

To add to that - containers are tested using CI/CD tools anyhow, which are predominantly powered by linux machines, which again makes this decision less convincing. The build may be fine on the developers machine and in production, but the CI/CD environment wouldn't reflect both of these environments.

This looks more like a facade for selling more Docker EE licenses rather than wanting to protect users. Which is fine, of course - but then please say that.

[InTheArena]

Yes, but think about the whipping we would (and have) given them in the past for bundling these things directly into the engine without sufficient time for testing, or good sep of concerns.

[rsanders]

There has been plenty of hue and cry in the past about the rapid rate of change of Docker, and new features bundled in when many users would have preferred a more deliberate and planned change in what is to them a critical piece of infrastructure. You're assuming quite a lot.

[ntnn]

If they were to plan this over a longer period of time for all distributions CE is available for I wouldn't have said anything. However they are specifically leaving out the platform most people are using docker on. And not only that - they _are_ providing k8s support with EE on linux. That pretty much deliberately points towards 'buy docker ee if you want this specific feature'.

Tbh, I wouldn't even have said anything if they were making that an EE-only feature. Thing is - they want to make money with that move and they're not honest about it. And in the process they're throwing the larger demograph using docker on the bleeding edge side of things in the mud. The people who are trying the new features on their own servers in their own time.

> There has been plenty of hue and cry in the past about the rapid rate of change of Docker

Yes, well - that is what happens when a company decides to use bleeding-edge hipster software. With puppet one minor version may not work with the server whos a few minors behind, with ELK in pre-5 versions the cluster may have gone keel over if the migration of the version hadn't been planned meticularly, with consul you may get better performance (dc-local speaking) than with etcd on one release and way worse the next.

Crying to the devs not to produce good software so quickly shouldn't be the solution.