-
Notifications
You must be signed in to change notification settings - Fork 715
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
kinder: switch all workflows to containerd #2620
kinder: switch all workflows to containerd #2620
Conversation
Switch all e2e test workflows to use containerd as the CR for the time being. Dockershim is being removed from k/k and until cri-dockerd gains maintainer traction we should avoid setting up our selfs for the sake of testing Docker as the CR. Technically the dockershim removal only affects "latest" workflows but this change will apply it to all k/k branches. Once and if cri-dockerd is testable we can add a single workflow for Docker as the CR.
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: neolit123 The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
hm...could be a flake calling --version in the etcd containers |
seems to not fail locally. |
+1 to this change |
/test pull-kubeadm-kinder-upgrade-latest |
not reproducible locally log:
in the failure logs, etcd pods appear to be running after the upgrade, so this might be caused by some weird kubectl exec semantic vs container state on a slower system (i.e. CI is slower) after the upgrade in the workflow... it might be worth waiting in a loop for ~10 seconds for if that also doesn't work this has to be removed from cluster-info: kubeadm/kinder/pkg/cluster/manager/actions/cluster-info.go Lines 59 to 99 in ecb3d22
|
/retest |
During CI the cluster-info fails with 'etcd --version' exiting with status 1, but locally this cannot be reproduced. Retry the command 10 times to try to avoid flakes.
b21774a
to
6fe0dde
Compare
i think this may have been a weird kubekins problem, because i saw some kubekins revert PRs in test-infra. regardless the cluster-info code now has retries: |
self-LGTM-ing since all docker jobs will start failing..... |
Switch all e2e test workflows to use containerd as the CR for the time
being. Dockershim is being removed from k/k and until cri-dockerd
gains maintainer traction we should avoid setting it up our selfs
for the sake of testing Docker as the CR.
Technically the dockershim removal only affects "latest" workflows
but this change will apply it to all k/k branches. Once and if
cri-dockerd is testable we can add a single workflow for Docker
as the CR.
xref #1412 (comment)