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
18.09: kubernetes: 1.10.5 -> 1.11.3 #46598
Conversation
Fixed minor issue where kube-addon manager complaints about /opt/namespace.yaml missing. Added release notes with reference to Kubernetes 1.11 release notes. closes NixOS#43882 (cherry picked from commit a49f56c)
Success on x86_64-darwin (full log) Attempted: kubernetes Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: kubernetes Partial log (click to expand)
|
@GrahamcOfBorg test kubernetes.rbac.singlenode kubernetes.dns.singlenode kubernetes.rbac.multinode kubernetes.dns.multinode |
No attempt on aarch64-linux (full log) The following builds were skipped because they don't evaluate on aarch64-linux: tests.kubernetes.rbac.singlenode, tests.kubernetes.dns.singlenode, tests.kubernetes.rbac.multinode, tests.kubernetes.dns.multinode Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: kubernetes Partial log (click to expand)
|
Success on x86_64-linux (full log) Attempted: tests.kubernetes.rbac.singlenode, tests.kubernetes.dns.singlenode, tests.kubernetes.rbac.multinode, tests.kubernetes.dns.multinode Partial log (click to expand)
|
Right on, I'm going on the assumption that 1.10 → 1.11 is right, as long as it's compatible (which you said it is). I'm assuming the 1.10 series may not receive updates, though I don't know what's the support cycle of kubernetes. Though it looks like they support the three latest versions. So it's not critical, but a fine addition to update to 1.11. Additionally they say they are generally compatible with some skew in the versions. And last, the first 1.11 release is from before the 18.09 branch-off, so it's double-plus-good to integrate it, as users would probably expect "latest stable version at the moment the OS version branched off". 👍 |
Backport of #46573 to 18.09. The module revamp did not make the cut for this release. See the comments on that PR for compatibility, namely that 1.11 works with our current modules (with the same issues that 1.10 has) and keeps us up to date.
@samueldr I assume this is still an acceptable backport, as long as we don't touch the module, right?
(cherry picked from commit a49f56c)
Motivation for this change
Things done
sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)nix path-info -S
before and after)