Kicbase: Switch ubuntu jammy to debian bookworm

[medyagh]

• Must be merged after Refactor Invoking Kubeadm command to prepare for debian 12 #21642
• To install new Containerd2 we need to bump our Base image
• Also newer Crio doesnt have repos for ubuntu jammy
• Kind also moved to debian 12 that we share the same entrypoint.sh (almost)

Commits Summary

• change ubuntu name to debian in code base
• update automation update tool for kicbase
• capitalize AS in Docker instructions
• enable RSA1 support in sshd config in debian dockerfile
• config Docker user for Passwordless login and add to corect groups
• install latst version of crio available in debian repos
• update docker installation for debian based on docker docs
• add crictl installation seprately since it is no longer shipped with crio
• remove old workarrounds

Previous Attempts:

• wip: Switch kicbase base image from "ubuntu jammy" to "debian bookworm" #21591
• As tested in Kicbase: bump ubuntu from jammy to noble #21537 ubuntu noble takes twice the time to build and one of the reasons to move to debian

Todos:

Move from RSA1 to a RSA2
#21543

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: medyagh

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:

• OWNERS [medyagh]

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

[medyagh]

/ok-to-build-image

[nirs]

This must be merged together with #21409 since the preloads created with containerd 1.7 may not be correct for containerd 2.

[medyagh]

This must be merged together with #21409 since the preloads created with containerd 1.7 may not be correct for containerd 2.

this doesnt touch iso, Containerd2 work can be done After this PR

[nirs]

This must be merged together with #21409 since the preloads created with containerd 1.7 may not be correct for containerd 2.

this doesnt touch iso, Containerd2 work can be done After this PR

When we update the base image we get a new version of containerd, so we ned to update also nerdctl. And since we share the preloads, we may need the same version of containerd in kicbase and iso. If this change does not bring contianerd v2 we are fine.

[medyagh]

/ok-to-build-image

[minikube-bot]

Hi @medyagh, we have updated your PR with the reference to newly built kicbase image. Pull the changes locally if you want to test with them or update your PR further.

[medyagh]

/ok-to-build-image

[medyagh]

/ok-to-test

[minikube-bot]

Hi @medyagh, we have updated your PR with the reference to newly built kicbase image. Pull the changes locally if you want to test with them or update your PR further.

[medyagh]

/ok-to-build-image

[minikube-bot]

Hi @medyagh, we have updated your PR with the reference to newly built kicbase image. Pull the changes locally if you want to test with them or update your PR further.

[medyagh]

/ok-to-test

[medyagh]

/ok-to-build-image

[minikube-bot]

Hi @medyagh, we have updated your PR with the reference to newly built kicbase image. Pull the changes locally if you want to test with them or update your PR further.

[k8s-ci-robot]

@medyagh: The following test failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
pull-minikube-integration	cc42fd2	link	true	/test pull-minikube-integration

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.

Instructions 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.

[minikube-pr-bot]

kvm2 driver with docker runtime

┌────────────────┬──────────┬────────────────────────┐
│    COMMAND     │ MINIKUBE │ MINIKUBE  ( PR 21643 ) │
├────────────────┼──────────┼────────────────────────┤
│ minikube start │ 41.4s    │ 42.9s                  │
│ enable ingress │ 15.9s    │ 15.7s                  │
└────────────────┴──────────┴────────────────────────┘

Times for minikube ingress: 15.8s 15.8s 15.8s 15.8s 16.3s
Times for minikube (PR 21643) ingress: 15.8s 15.8s 15.8s 16.3s 14.8s

Times for minikube start: 39.8s 39.9s 41.2s 43.7s 42.2s
Times for minikube (PR 21643) start: 42.1s 46.1s 42.0s 42.2s 42.3s

docker driver with docker runtime

┌────────────────┬──────────┬────────────────────────┐
│    COMMAND     │ MINIKUBE │ MINIKUBE  ( PR 21643 ) │
├────────────────┼──────────┼────────────────────────┤
│ minikube start │ 23.1s    │ 23.3s                  │
│ enable ingress │ 11.0s    │ 11.4s                  │
└────────────────┴──────────┴────────────────────────┘

Times for minikube ingress: 10.6s 10.6s 10.6s 10.6s 12.6s
Times for minikube (PR 21643) ingress: 10.6s 12.7s 10.6s 12.6s 10.6s

Times for minikube start: 22.7s 22.9s 21.5s 25.4s 23.2s
Times for minikube (PR 21643) start: 21.5s 22.2s 23.8s 24.0s 25.0s

docker driver with containerd runtime

┌────────────────┬──────────┬────────────────────────┐
│    COMMAND     │ MINIKUBE │ MINIKUBE  ( PR 21643 ) │
├────────────────┼──────────┼────────────────────────┤
│ minikube start │ 20.3s    │ 23.1s                  │
│ enable ingress │ 26.5s    │ 21.3s                  │
└────────────────┴──────────┴────────────────────────┘

Times for minikube ingress: 40.1s 23.1s 23.1s 23.1s 23.1s
Times for minikube (PR 21643) ingress: 21.1s 21.1s 21.1s 22.1s 21.1s

Times for minikube start: 18.8s 21.8s 21.5s 20.1s 19.5s
Times for minikube (PR 21643) start: 24.6s 23.3s 22.2s 23.7s 22.0s

[minikube-pr-bot]

Here are the number of top 10 failed tests in each environments with lowest flake rate.

Environment	Test Name	Flake Rate
Docker_Linux_containerd (9 failed)	TestFunctional/parallel/DashboardCmd(gopogh)	0.00% (chart)
Docker_Linux_containerd (9 failed)	TestFunctional/parallel/ServiceCmdConnect(gopogh)	0.00% (chart)
Docker_Linux_containerd (9 failed)	TestFunctional/parallel/PersistentVolumeClaim(gopogh)	0.00% (chart)
Docker_Linux_containerd (9 failed)	TestFunctional/parallel/TunnelCmd/serial/WaitService/Setup(gopogh)	0.00% (chart)
Docker_Linux_containerd (9 failed)	TestFunctional/parallel/ServiceCmd/DeployApp(gopogh)	0.00% (chart)
Docker_Linux_containerd (9 failed)	TestFunctional/parallel/TunnelCmd/serial/AccessDirect(gopogh)	0.00% (chart)
Docker_Linux_containerd (9 failed)	TestFunctional/parallel/ServiceCmd/HTTPS(gopogh)	0.00% (chart)
Docker_Linux_containerd (9 failed)	TestFunctional/parallel/ServiceCmd/Format(gopogh)	0.00% (chart)
Docker_Linux_containerd (9 failed)	TestFunctional/parallel/ServiceCmd/URL(gopogh)	0.00% (chart)
Docker_Linux_docker_arm64 (1 failed)	TestScheduledStopUnix(gopogh)	8.16% (chart)
Docker_Windows (1 failed)	TestErrorSpam/setup(gopogh)	Unknown

Besides the following environments also have failed tests:

• KVM_Linux_crio: 14 failed (gopogh)

• Docker_Linux_containerd_arm64: 12 failed (gopogh)

• Docker_Linux_crio: 56 failed (gopogh)

• Docker_Linux_crio_arm64: 47 failed (gopogh)

To see the flake rates of all tests by environment, click here.

[medyagh]

Docker Linux Passes
Docker Linux Containerd Failures are Docker hub Rate limits it passed in previous commit

Docker Linux Crio is meant to be fixed by community or droped from minikube