I don't work with K8S or even docker on a day-to-day basis, but to me the ecosystem looks rather good. There are several solutions of orchestration and containerization competing from different vendors, and things tend to be standardised to make them work together :
- https://github.com/kubernetes/community/blob/master/contribu...
- https://www.opencontainers.org/
No later than yesterday there was that post on HN : https://news.ycombinator.com/item?id=18050781
People experiment, dissect, keep some old things, hack new things. K8S is still in active development, new initiatives like Istio and Knative are built on top of it. It looks like an healthy innovative ecosystem to me. I guess it depends of point of view and interests.
No IPv6 support in it at all, and the company seems to have moved resources internally away from Swarm development.
Doesn't bode well for it's future. Expecting it'll be taken out to the back shed (-bang-) in a while.
With no actual announcement(s) then occurring.
The commit activity graph on InfraKit - which people are supposed to use now that Docker-Machine has been deprecated - seems pretty clear:
https://github.com/docker/infrakit/graphs/contributors
SwarmKit is the same:
https://github.com/docker/swarmkit/graphs/contributors
Clearly these aren't where resources have been placed.
Actions are not lining up with the words given. :(
This stack doesn't offer all of the same functionality as the Kubernetes ecosystem, but it has the benefit of being vastly simpler and composed of relatively small, independent parts.
We did examine Kubernetes, but for various reasons we need to manage our own cluster and the engineering overhead was too high for our team to take on.