pickup containerd 2.2.1 and bookworm#4086
pickup containerd 2.2.1 and bookworm#4086BenTheElder wants to merge 6 commits intokubernetes-sigs:mainfrom
Conversation
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: BenTheElder The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/hold |
|
Was looking into the kubeadm v1beta4 stuff ... took a quick look here, PVs are broken, will need to investigate further. |
inside the local path provisioner https://storage.googleapis.com/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_kind/4086/pull-kind-e2e-kubernetes/2002170163704631296/artifacts/kind-control-plane/pods/local-path-storage_local-path-provisioner-9cc47865c-x8jdl_a30574b4-0f3b-4584-9f1c-26b49ad09f47/local-path-provisioner/0.log
a possible problem with pkg/build/nodeimage/const_storage.go ? It seems the kubelet can not start those helper pods https://storage.googleapis.com/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_kind/4086/pull-kind-e2e-kubernetes/2002170163704631296/artifacts/kind-worker/kubelet.log |
|
Yeah it's definitely something with the updated storage driver images, not enough logs to tell from CI. Will replicate later. |
|
|
|
#4103 for image fixes, then we can try this again |
2f20921 to
486c51a
Compare
|
@BenTheElder: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
#4103 replaces this |
clears up some logspam via containerd/containerd#12579
haproxy and local-path provisioner: #4003 + #4081
tested locally to confirm logspam fix and verify multiple control plane nodes work with the new haproxy
note: last commit currently uses a staging node image, to exercise github actions
were we to release to users at least, we'd want to promote it to kindest/node first and switch to that