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.9.1 -> 1.10 #38445
kubernetes: 1.9.1 -> 1.10 #38445
Conversation
Success on x86_64-linux (full log) Attempted: kubernetes Partial log (click to expand)
|
Success on aarch64-linux (full log) Attempted: kubernetes Partial log (click to expand)
|
I'm wondering why this PR is not moving, it seems to look fine. |
Sorry, I completely forgot I had been pinged for review. I am not in a position to actually test kubernetes anymore, but the changes look sane to me and I am very happy to see the flags moving into a config file! |
The tests seem to run indefinitely without success, including the singlenode ones.
At this point I can't tell if it's a misconfiguration or upstream issues that prevent the setup from working, I'm afraid I have to leave this one to the more experienced, as I don't have that much spare time to debug this. My changes and the logs of running the dns.singlenode tests are in a gist: https://gist.github.com/steveeJ/8abeb3c02a85aeeb1113969bec84541b |
@steveej where you got the infos about how to run the testsuite? |
@azazel75 it's part of the nixos test expressions, which I wasn't familiar with at that point.
I can't reproduce my above result at the moment, instead I'm getting this error:
|
@steveej and others. Have a look at my branch here: https://github.com/johanot/nixpkgs/tree/kube-1.10 .. I did the following:
Can you verify that the test cases run clean for you after pulling my changes? If so, we can start squashing/cherry-picking. :) |
Ah, @johanot , you beat me! I too have a similar branch here https://github.com/azazel75/nixpkgs/tree/kube-1.10 . All the enabled tests pass. From what I can see, the differences between ou two branches are the follow:
|
Great! Just to know, what's the policy for the update of packages in 18.03 in Nixos? i.e. will this land on 18.03 or I will have to backport it myself? Keeping a server on unstable is a bad idea :-) |
@azazel75 I am not keen on backporting what is essentially a major version in Kubernetes' terms to stable. You can however pull in these changes on top of your existing 18.03 server. |
Good work, everyone!
I don’t have the bandwidth to keep pushing this PR forward. I’d
recommend opening a new PR and closing this one. Might be a good idea to
mention this PR’s number in the new one, so the above thread of
communication can be found easily.
On Wed, May 23, 2018, at 4:43 PM, Stefan Junker wrote:
@johanot[1] @azazel75[2] this is great news, thanks to both of you!
I ran the dns and rbac tests locally against @johanot[3]'s kube-1.10
branch with success.> @cstrahan[4] would it be possible for you to incorporate the changes
discussed above or would you prefer to close this PR?> — You are receiving this because you were mentioned. Reply to this
email directly, view it on GitHub[5], or mute the thread[6].
|
Closing this in favour of #41073. Thanks for the effort everyone! |
Motivation for this change
Updates to latest kubernetes release.
The patches were removed, as they're now applied in the latest release.
Things done
build-use-sandbox
innix.conf
on non-NixOS)nix-shell -p nox --run "nox-review wip"
./result/bin/
)/cc @srhb @matejc @offlinehacker