updating all images to latest

[BenTheElder]

picks up assorted updates ahead of v0.31.0

[BenTheElder]

we could update again with #3965 but I think it's not critical

[BenTheElder]

smoke tested locally, seems fine.

$ cat $HOME/kind-ha.yaml 
kind: Cluster
apiVersion: kind.x-k8s.io/v1alpha4
nodes:
- role: control-plane
- role: control-plane
- role: control-plane

$ kind create cluster --config=$HOME/kind-ha.yaml 
Creating cluster "kind" ...
 ✓ Ensuring node image (kindest/node:v1.34.2) 🖼 
 ✓ Preparing nodes 📦 📦 📦  
 ✓ Configuring the external load balancer ⚖️ 
 ✓ Writing configuration 📜 
 ✓ Starting control-plane 🕹️ 
 ✓ Installing CNI 🔌 
 ✓ Installing StorageClass 💾 
 ✓ Joining more control-plane nodes 🎮 
Set kubectl context to "kind-kind"
You can now use your cluster with:

kubectl cluster-info --context kind-kind

Not sure what to do next? 😅  Check out https://kind.sigs.k8s.io/docs/user/quick-start/

$ kubectl get po -A
NAMESPACE            NAME                                          READY   STATUS    RESTARTS   AGE
kube-system          coredns-66bc5c9577-26ct8                      1/1     Running   0          50s
kube-system          coredns-66bc5c9577-sw2p8                      1/1     Running   0          50s
kube-system          etcd-kind-control-plane                       1/1     Running   0          58s
kube-system          etcd-kind-control-plane2                      1/1     Running   0          24s
kube-system          etcd-kind-control-plane3                      1/1     Running   0          14s
kube-system          kindnet-86km5                                 1/1     Running   0          16s
kube-system          kindnet-qnkn8                                 1/1     Running   0          26s
kube-system          kindnet-xks7f                                 1/1     Running   0          50s
kube-system          kube-apiserver-kind-control-plane             1/1     Running   0          58s
kube-system          kube-apiserver-kind-control-plane2            1/1     Running   0          24s
kube-system          kube-apiserver-kind-control-plane3            1/1     Running   0          14s
kube-system          kube-controller-manager-kind-control-plane    1/1     Running   0          58s
kube-system          kube-controller-manager-kind-control-plane2   1/1     Running   0          24s
kube-system          kube-controller-manager-kind-control-plane3   1/1     Running   0          14s
kube-system          kube-proxy-f6mvv                              1/1     Running   0          26s
kube-system          kube-proxy-s4nj7                              1/1     Running   0          16s
kube-system          kube-proxy-vvtk5                              1/1     Running   0          50s
kube-system          kube-scheduler-kind-control-plane             1/1     Running   0          58s
kube-system          kube-scheduler-kind-control-plane2            1/1     Running   0          24s
kube-system          kube-scheduler-kind-control-plane3            1/1     Running   0          14s
local-path-storage   local-path-provisioner-5c4cdb564f-cfbcj       1/1     Running   0          49s

[stmcginnis]

/lgtm

[BenTheElder]

Ah, that's going to be a problem ...

[BenTheElder]

https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_kind/4069/pull-kind-e2e-kubernetes-1-33/1999557331033001984

is kubernetes/kubernetes#135214

[BenTheElder]

Only 1.33 is impacted, we can consider something like configuring CI to skip these tests on 1.33, but we need to discuss in kubernetes/kubernetes#135214

[BenTheElder]

should do 1.34.3

[BenTheElder]

trying runc 1.2.x in CI here

[BenTheElder]

Ok, so we can use runc 1.2.x as a stopgap, but eventually this is a problem because we're not aligned with containerd, and runc is already on 1.4.0 now.

We really need a better solution to kubernetes/kubernetes#135214

[BenTheElder]

/retest pull-kind-e2e-kubernetes-1-31

seems to be a minor flake, one test case

[BenTheElder]

/retest

[stmcginnis]

Jobs are happy, looks good.

/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: BenTheElder, stmcginnis

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details

Needs approval from an approver in each of these files:

• OWNERS [BenTheElder,stmcginnis]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[BenTheElder]

ceffaf4

We upgraded to runc 1.3.0 in kind v0.28, so this kind of stinks, but it is a ~fully patched runc release that does not break 1.33 tests.

If I had more time, I'd fix the 1.33 tests, but I want to get us ready for k8s 1.35, and runc 1.2.9 should be OK for now.

[BenTheElder]

Thankfully after that we did not upgrade again until a5cac99 which never released, so hopefully it's not a big deal in the short term.

1.2.x will be losing support though, so we do have to move once the tests are sorted.