-
Notifications
You must be signed in to change notification settings - Fork 777
Description
New repo, staging repo, or migrate existing
(migrating from minikube's hack folder to its own repo)
Is it a staging repo?
yes
Requested name for new repository
minikube-preloads
Which Organization should it reside
kubernetes
Who should have admin access?
medyagh
Who should have write access?
medyagh
Who should be listed as approvers in OWNERS?
medyagh
Who should be listed in SECURITY_CONTACTS?
medyagh
What should the repo description be?
Preloaded images for Kubernetes version for each container runtime and cpu architecture and filesystem.
What SIG and subproject does this fall under?
sig-cluster-lifecycle
Please provide references to appropriate approval for this new repo
Currently minikbue's release build infra is inside an internal google GCP project that I we are trying to migrate to public owned infrastructure.
minikube produces Preloaded Images Tar Files Per Kubernetes Version that is Shared between VM Drivers and KIC drivers (kubernetes in container).
Each Tar file is combination of preloaded images for a specific Kubernetes Version - Specific Runtime (docker,contained, crio) - File System - and CPU arch (x86 or arm64)
and these combinations are produced for every Kubernetes version
currently residing in a Google-owned GCS bucket
we would like this to move to a github assets released by github actions
Currently minikbue's release build infra is inside an internal google GCP project that I we are trying to migrate to public owned infrastructure.
Additional context for request
kubernetes/minikube#2092
No response