Change:
warn: false, }, { <del> name: "Docker version 19.01.0 is not in the list of validated versions", info: dockerInfo{Driver: "driver_2", ServerVersion: "19.01.0"}, </del> <ins> name: "valid Docker version 19.03.1-ce", info: dockerInfo{Driver: "driver_2", ServerVersion: "19.03.1-ce"}, err:  false, warn: false, }, { name: "Docker version 19.06.0 is not in the list of validated versions", info: dockerInfo{Driver: "driver_2", ServerVersion: "19.06.0"}, </ins> err:  false, warn: true, },

Discussion:
<!-- Please only use this template for submitting enhancement requests --What would you like to be : Support for newer docker versions: 19.x Why is this needed: New users trying to use kubernetes install the latest docker version. It's inconvenient see the following warning and have to uninstall docker and then install an older version. Also, it's not clear what could happen if someone uses a newer version of docker. Lastly, I believe that kubernetes should be able to keep up with docker. Is there any roadmap for this, that I have missed?
/sig usability
you could work with sig-testing and sig-node to set up CI jobs when new versions of Docker shows up. Believe me, it's more inconvenient to debug failures in a new docker version as a end use than the downgrade. We have to have some CI coverage of a version before we ok its use by the community.
Hi I'm new to this, so I'm not sure how to apply your suggestion: Is there any documentation that I could use?
SIGs are teams working on specific areas of kubernetes All our test infrastructure for CI jobs ("Continuous Integration") is in: Out test-grid is here (please type docker in the search box on top to see the current CI jobs):
Since docker-ce 18.09 has reached EOL and there are no new versions planned (), it would be great to have official support for a newer version of docker-ce.
please see:
Hi folks, David from Docker here, we have run and validated Docker Engine 19.03 for Kubernetes 1.14 back in June, so Docker 19.03 is indeed supported for Kubernetes 1.14 and above: Let me know how else we can help.
thanks for confirming PR is here
Thank you Appreciate the PR, we typically test engines for major versions of Engine that are released like 19.03 with the latest version of Kubernetes that is available at the time. On our next engine, we will re-run the test and submit the results to testgrid. Let me know how I can better coordinate this.
Also let me know if there is anything else that is needed to close this issue out. Thanks.
hi, the PR should close this issue. i guess, one option is just creating a similar issue once the test job is available in test-grid and running green for a while? or me can then proceed to update the validators.

Ok thank you, that sounds like a good process we can follow moving forward.
Hi Any chance this can make its way into 1.16 at least? This way it may get picker up by Kops and not have to rely on some old and unpatched Docker version. At the moment Docker CE 18.09 is no longer actively supported
hi, we cannot backport this as it's not a critical fix. at least in the case of kubeadm the 19. versions of docker would only print a warning.
but doesn't the existence of a vulnerability make this critical enough?
the usage of Docker 19. is not blocked in any way in 1.16. you can ignore the and just use it. if something was blocking the usage of 19., then this is backport worthy.
I saw this as the first step before adding 19.03 as a validated external release. Without being documented as such Kops will not pick it up as default and will leave people with old and vulnerable Docker versions. If this I understand correctly the above comments, 19.03 has been validated for some time, just not documented.
i don't think kops uses the kubeadm validators that reside in k/k/cmd/kubeadm/app/... this was resolved in this PR the k8s docs for CRI are still out of date: so if someone wants to send a PR for that page please go ahead: (but AFAIK not all distros have moved to 19. yet)
I couldn't find any repos missing docker 19.03.4. Any chance to do the change in the changelog?