-
Notifications
You must be signed in to change notification settings - Fork 3.4k
v1.6 backports 2020-09-02 #13054
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
v1.6 backports 2020-09-02 #13054
Conversation
[ upstream commit 85600be ] This PR is to correct simple typo equal in metrics.rst Signed-off-by: Tam Mach <sayboras@yahoo.com> Signed-off-by: Chris Tarazi <chris@isovalent.com>
[ upstream commit eeec4d0 ] Signed-off-by: Nicolas Jacques <neela@isovalent.com> Signed-off-by: Chris Tarazi <chris@isovalent.com>
[ upstream commit 6711a0c ] Fixes copy button to not conflict with the search Signed-off-by: Sergey Generalov <sergey@genbit.ru> Signed-off-by: Chris Tarazi <chris@isovalent.com>
[ upstream commit 552c823 ] [ Backporter's notes: The original change contains two locations where the check for crictl.yaml needed to be modified. In the v1.6 tree, only one location contains a reference to crictl.yaml, and this commit modifies it. ] This script has several tests for what the container runtime situation looks like to determine how best to restart the underlying containers (going around the kubelet) so that the new networking configuration can take effect. The first test looks to see if the crictl config file is configured to use docker, but if that file doesn't exist then it fails. I believe docker is the default if this hasn't been configured at all so if that file doesn't exist then use docker. Fixes #12850 Signed-off-by: Nathan Bird <njbird@infiniteenergy.com> Signed-off-by: Chris Tarazi <chris@isovalent.com>
test-backport-1.6 Edit: VM provisioning failure. |
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.
Looks good for my changes 👍
test-backport-1.6 Edit: VM provisioning failure again. |
test-backport-1.6 |
v1.6 cert expiry issue still. Looking at the changes being made here, I think I'm happy to accept these backports in without CI since CI is unlikely to catch anything here (+ these already ran against other branches). @aanm does this sound reasonable to you? One of the benefits here in particular would be fixing up search for v1.6 branch. |
@joestringer LGTM |
Once this PR is merged, you can update the PR labels via: