The image list is broken again, for kubernetes version 1.28.0

[afbjorklund]

This is because minikube 1.31.1 does not include the new constants, and because the fallback is broken:

actual:

├── images
│   └── amd64
│       ├── gcr.io
│       │   └── k8s-minikube
│       │       └── storage-provisioner_v5
│       └── registry.k8s.io
│           ├── coredns
│           │   └── coredns_v1.9.4
│           ├── etcd_v3.3.8-0-gke.1
│           ├── kube-apiserver_v1.28.0-rc.0
│           ├── kube-controller-manager_v1.28.0-rc.0
│           ├── kube-proxy_v1.28.0-rc.0
│           ├── kube-scheduler_v1.28.0-rc.0
│           └── pause_test2

expected:

registry.k8s.io/kube-apiserver:v1.28.0-rc.0
registry.k8s.io/kube-controller-manager:v1.28.0-rc.0
registry.k8s.io/kube-scheduler:v1.28.0-rc.0
registry.k8s.io/kube-proxy:v1.28.0-rc.0
registry.k8s.io/pause:3.9
registry.k8s.io/etcd:3.5.9-0
registry.k8s.io/coredns/coredns:v1.10.1

The etcd and pause are the biggest problems, since they are for the wrong architecture (amd64 only).

• Wrong image versions used for some of the kubeadm images in 1.26 #15494
• Minikube >= 1.30.0 generates /etc/systemd/system/cri-docker.service.d/10-cnf.conf with wrong pause image on arm64 when using --driver=none #16823

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle rotten
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue, marking it as "Not Planned".

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue with /reopen
• Mark this issue as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close not-planned

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/test-infra repository.