Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Remove support for Docker 1.11, 1.12 and 1.13 #8855

Merged
merged 1 commit into from
Apr 7, 2020

Conversation

hakman
Copy link
Member

@hakman hakman commented Apr 6, 2020

The repo containing the binaries for Docker 1.11, 1.12 and 1.13 was shut down on March 31. This means support for older docker versions cannot be maintained.
https://www.docker.com/blog/changes-dockerproject-org-apt-yum-repositories/

On the 31st of March 2020, we will be shutting down the legacy APT and YUM repositories hosted at dockerproject.org and dockerproject.com. These repositories haven’t been updated with the latest releases of Docker and so the packages hosted there contain security vulnerabilities. Removing these repositories will make sure that people download the latest version of Docker ensuring their security and providing the best experience possible

This PR will need to be cherry-picked to 1.16+.

@k8s-ci-robot k8s-ci-robot added cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/M Denotes a PR that changes 30-99 lines, ignoring generated files. labels Apr 6, 2020
@hakman
Copy link
Member Author

hakman commented Apr 6, 2020

This should be the simplest thing that can be cherry-picked to 1.16+.
#8846 (comment)

@hakman
Copy link
Member Author

hakman commented Apr 6, 2020

/cc @rifelpet

allErrs = append(allErrs, field.Invalid(fldPath.Child("version"), config.Version,
"version is no longer available: https://www.docker.com/blog/changes-dockerproject-org-apt-yum-repositories/"))
} else {
valid := []string{"17.03.2", "17.09.0", "18.03.1", "18.06.1", "18.06.2", "18.06.3", "18.09.3", "18.09.9", "19.03.4", "19.03.8"}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

What used to happen if a user specified a version that was not in this list? like 18.09.8 for example.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Any Docker version would have been accepted and NodeUp would fail if it was not listed.
It can still fail as not all versions have support for all distros.

Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

hm does that mean that if a specific version of docker was already installed in the AMI and a user specified a version not in this list, they used to have a functioning cluster with their docker version but now their update cluster command would fail? I'm just trying to think through any concerns with adding this validation...

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If a specific Docker version is install on a AMI, skipInstall would have been used and the Docker version would not matter much, I guess.

@rifelpet
Copy link
Member

rifelpet commented Apr 7, 2020

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Apr 7, 2020
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: hakman, rifelpet

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 7, 2020
@k8s-ci-robot k8s-ci-robot merged commit 4d174db into kubernetes:master Apr 7, 2020
@k8s-ci-robot k8s-ci-robot added this to the v1.18 milestone Apr 7, 2020
k8s-ci-robot added a commit that referenced this pull request Apr 7, 2020
k8s-ci-robot added a commit that referenced this pull request Apr 7, 2020
…pstream-release-1.16

Automated cherry pick of #8855: Remove support for Docker 1.11, 1.12 and 1.13
k8s-ci-robot added a commit that referenced this pull request Apr 7, 2020
…pstream-release-1.17

Automated cherry pick of #8855: Remove support for Docker 1.11, 1.12 and 1.13
@hakman hakman deleted the remove-docker-1.1x branch April 30, 2020 11:43
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. area/api cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. lgtm "Looks good to me", indicates that a PR is ready to be merged. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants