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
kubernetes: 1.17.3 -> 1.18.0 #83984
kubernetes: 1.17.3 -> 1.18.0 #83984
Conversation
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
LGTM, let's give us some time for manual testing.
I did not see any big changes in the changelogs which could have affect on our side, but I could be wrong for sure.
Looks good from my side, can we get this into 20.3? :) |
LGTM too. However, one should really take note of this changelog entry in particular when upgrading:
I don't have any feeling of whether it's too late to for this to make it into 20.03. I'll let others decide of that. :) But merge to master, definitely. |
Note that those APIs defaulted off in 1.16, and 1.18 makes that default behavior permanent. Unless you were explicitly overriding the defaults to re-enable in 1.16/1.17, this won't affect you. |
Thank you for the clarification Jordan! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Tested this on my AWS cluster and it's working as expected 👍
LGTM too. Whether this should be backported to 20.03 I'm not sure. I propose that we open an issue and deal with this discussion once and for all. I am inclined to say: Let's leave it up to the release managers for now. Then, for 20.09, add release notes that clarify that NixOS releases will now track the latest major release of kubernetes, even within the stable release, due to the speed at which Kubernetes releases. The alternative, I think, is tracking ~2 kubernetes releases and switching around the default one every major release, but I think that's too much busywork. |
Semi-automatic update generated by nixpkgs-update tools. This update was made based on information from https://github.com/kubernetes/kubernetes/releases.
meta.description for kubernetes is: "Production-Grade Container Scheduling and Management"
meta.homepage for kubernetes is: "https://kubernetes.io"
Updates performed:
Release on GitHub
Compare changes on GitHub
Checks done (click to expand)
built on NixOS
The tests defined in
passthru.tests
, if any, passed0 of 0 passed binary check by having a zero exit code.
0 of 0 passed binary check by having the new version present in output.
found 1.18.0 with grep in /nix/store/p385jskppw4i9qpcn407mr5jbvjvhw3s-kubernetes-1.18.0
directory tree listing: https://gist.github.com/540bf289b63f40f45c46d459f060d01e
du listing: https://gist.github.com/d5c868af575dec95e633f38d4ff2c6a4
Rebuild report (if merged into master) (click to expand)
12 total rebuild path(s)
3 package rebuild(s)
3 x86_64-linux rebuild(s)
3 i686-linux rebuild(s)
3 x86_64-darwin rebuild(s)
3 aarch64-linux rebuild(s)
First fifty rebuilds by attrpath
kubectl
kubectx
kubernetes
Instructions to test this update (click to expand)
Either download from Cachix:
(r-ryantm's Cachix cache is only trusted for this store-path realization.)
For the Cachix download to work, your user must be in the
trusted-users
list or you can usesudo
since root is effectively trusted.Or, build yourself:
After you've downloaded or built it, look at the files and if there are any, run the binaries:
cc @johanot @offlinehacker @saschagrunert for testing.