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.

Sign up for GitHub

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

Jump to bottom

Update CoreDNS #2572

Closed
gdemonet opened this issue May 26, 2020 · 0 comments · Fixed by #2582
Closed

Update CoreDNS #2572

gdemonet opened this issue May 26, 2020 · 0 comments · Fixed by #2582
Assignees
@Ebaneck
Labels
kind:dependencies Pull requests that update a dependency file topic:build Anything related to building steps topic:deployment Bugs in or enhancements to deployment stages topic:lifecycle Issues related to upgrade or downgrade of MetalK8s
Milestone
MetalK8s 2.5.2

Comments

@gdemonet
Copy link
Contributor

Component: kubernetes, coredns

Why this is needed:

Our current deployed version of CoreDNS 1.3.1 (what kubeadm shipped with K8s 1.15), and was never updated ever since.

What should be done:

Every new minor release should get each addon updated to the kubeadm standard (which dependencies are changed is always described in the K8s release notes).

Implementation proposal (strongly recommended):

Versions mapping:

  • K8s 1.15 -> 1.3.1
  • K8s 1.16 -> 1.6.2
  • K8s 1.17 -> 1.6.5
  • K8s 1.18 -> 1.6.7

Test plan:
@gdemonet gdemonet added topic:deployment Bugs in or enhancements to deployment stages topic:build Anything related to building steps topic:lifecycle Issues related to upgrade or downgrade of MetalK8s kind:dependencies Pull requests that update a dependency file labels May 26, 2020
@gdemonet gdemonet added this to the MetalK8s 2.5.1 milestone May 26, 2020
@Ebaneck Ebaneck self-assigned this May 27, 2020
Ebaneck added a commit that referenced this issue May 27, 2020
@Ebaneck
deps: update coredns to version 1.6.2
36f55cb 
Our current deployed version for coredns is `1.3.1`
which seems to be very old.

Since we plan a minor release, we should bump the version of Coredns
to a recent release.

Note: since this branch runs K8S 1.16, we bind the coredns version
to `1.6.2` following same standards from kubeadm.

Closes: #2572
@Ebaneck Ebaneck mentioned this issue May 27, 2020
Merged
@Ebaneck Ebaneck mentioned this issue May 29, 2020
Merged
@bert-e bert-e closed this as completed in 7f51d59 Jul 7, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Ebaneck Ebaneck

Labels
kind:dependencies Pull requests that update a dependency file topic:build Anything related to building steps topic:deployment Bugs in or enhancements to deployment stages topic:lifecycle Issues related to upgrade or downgrade of MetalK8s
Projects
None yet
Milestone
MetalK8s 2.5.2
Development

Successfully merging a pull request may close this issue.

build(deps): bump coredns from 1.3.1 to 1.6.5 scality/metalk8s
2 participants
@Ebaneck @gdemonet