-
Notifications
You must be signed in to change notification settings - Fork 5.1k
Open
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.
Description
since this PR #21115 that we removed the fork to use upstream
"
the Sub Steps that shows kubernetes Creating Shows for 1 miliseconds and vanishes
"
here how it looks like
$ mk start -d krunkit
π minikube v1.36.0 on Darwin 15.5 (arm64)
β¨ Using the krunkit (experimental) driver based on user configuration
π Starting "minikube" primary control-plane node in "minikube" cluster
π Configuring bridge CNI (Container Networking Interface) ...
π Verifying Kubernetes components...
βͺ Using image gcr.io/k8s-minikube/storage-provisioner:v5
π Enabled addons: default-storageclass, storage-provisioner
π Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default
but it is missing to big blocks
π₯ Creating
and
π³ Preparing
here is output not from HEAD but from released minikiube
π minikube v1.36.0 on Darwin 15.5 (arm64)
β¨ Automatically selected the vfkit driver
π Starting "minikube" primary control-plane node in "minikube" cluster
π₯ Creating vfkit VM (CPUs=2, Memory=6000MB, Disk=20000MB) ...
β Image was not built for the current minikube version. To resolve this you can delete and recreate your minikube cluster using the latest images. Expected minikube version: v1.35.0 -> Actual minikube version: v1.36.0
π³ Preparing Kubernetes v1.33.1 on Docker 28.0.4 ...
βͺ Generating certificates and keys ...
βͺ Booting up control plane ...
βͺ Configuring RBAC rules ...
π Configuring bridge CNI (Container Networking Interface) ...
π Verifying Kubernetes components...
βͺ Using image gcr.io/k8s-minikube/storage-provisioner:v5
π Enabled addons: default-storageclass, storage-provisioner
π Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default```
the qeustion is what is difference of "π₯ Creating" and "π³ Preparing Kubernetes" blocks that if we use the fork (https://github.com/alonyb/spinner) it works fine but if we use upsteam https://github.com/briandowns/spinner
it doesnt work work
if we cant make it work we should Keep the old fork maybe Fork it again and bump the go mod dependecies to make it a bit more fresh https://github.com/alonyb/spinner
if @alonyb is still here can also comment :)
Metadata
Metadata
Assignees
Labels
kind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.Must be staffed and worked on either currently, or very soon, ideally in time for the next release.