Add preload tar files to the "released files" automatically.

[medyagh]

we should include the preload images in the release notes automaticly.

at least for the past 10 versions maybe

[tstromberg]

I don't understand this. What exactly would you like to see in CHANGELOG.md?

[medyagh]

oops I didnt mean release notes, I meant released attached files

[afbjorklund]

oops I didnt mean release notes, I meant released attached files

You mean the page on GitHub, or to the Google Cloud Storage ?

Currently we add some binaries only to the more "hidden" url.
Like for instance minikube for non-amd64 architectures and such.

We could also consider exposing the kicbase image ? #7012 (comment)

[afbjorklund]

@medyagh is this issue related to issues like #7695 ?

Because normally minikube will handle the preload downloading
(and should work just fine, but slower, if no preload is available)

Maybe we should also have a tarball, with only the images.

Like a more portable version of the preload, and without the binaries.
Then you could use it as an alternative, like with containerd/podman

• Preload containerd images  #6933 containerd preload
• Preload CRI-O images #6934 crio preload

[afbjorklund]

Will open two separate issues, for the non-preloaded alternatives

• kicbase (gcr.io/k8s-minikube/kicbase)
  • gcr.io/k8s-minikube/kicbase:v0.0.9
• minikube ( the essentials, like kubeadm config images list)
  • k8s.gcr.io/kube-apiserver:v1.18.2
    k8s.gcr.io/kube-controller-manager:v1.18.2
    k8s.gcr.io/kube-scheduler:v1.18.2
    k8s.gcr.io/kube-proxy:v1.18.2
    k8s.gcr.io/pause:3.2
    k8s.gcr.io/etcd:3.4.3-0
    k8s.gcr.io/coredns:1.6.7

Could even have variants using the OCI format (instead of docker)

podman save --format oci-archive

or with alternative compression formats (like lz4 or xz, instead of gz)

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

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.