search

loft-sh / loft

Namespace & Virtual Cluster Manager for Kubernetes - Lightweight Virtual Clusters, Self-Service Provisioning for Engineers and 70% Cost Savings with Sleep Mode
https://loft.sh/docs/introduction
Other
722 stars 64 forks source link

cannot install loft on minikube (Error during helm command) #73

Closed ghost closed 2 years ago

ghost commented 3 years ago

Hi guys,

Hope you are all well !

$ kubectl auth can-i create clusterrole -A
yes
$ loft start

[info]   Welcome to the loft installation.
[info]   This installer will guide you through the installation.
[info]   If you prefer installing loft via helm yourself, visit https://loft.sh/docs/getting-started/setup
[info]   Thanks for trying out loft!

? Seems like your cluster is running locally (docker desktop, minikube, kind etc.). Is that correct?
 Yes

? Enter an email address for your admin user michalski.luc@gmail.com

[info]   This will install loft without an externally reachable URL and instead use port-forwarding to connect to loft

[info]   Executing command: helm install loft loft --repository-config  --repo https://charts.devspace.sh/ --kube-context minikube --namespace loft --set certIssuer.create=false --set ingress.enabled=false --set cluster.connect.local=true --set admin.password=821b6889-1d39-4c44-b6e7-852a714f6a95 --set admin.email=michalski.luc@gmail.com --wait

[fatal]  Error during helm command: W1124 07:38:38.582665  517752 warnings.go:67] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
W1124 07:38:38.780785  517752 warnings.go:67] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
W1124 07:38:39.178691  517752 warnings.go:67] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
W1124 07:38:41.377876  517752 warnings.go:67] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
W1124 07:38:41.481505  517752 warnings.go:67] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
W1124 07:38:41.580392  517752 warnings.go:67] apiextensions.k8s.io/v1beta1 CustomResourceDefinition is deprecated in v1.16+, unavailable in v1.22+; use apiextensions.k8s.io/v1 CustomResourceDefinition
W1124 07:38:45.479906  517752 warnings.go:67] admissionregistration.k8s.io/v1beta1 ValidatingWebhookConfiguration is deprecated in v1.16+, unavailable in v1.22+; use admissionregistration.k8s.io/v1 ValidatingWebhookConfiguration
W1124 07:39:02.975126  517752 warnings.go:67] admissionregistration.k8s.io/v1beta1 ValidatingWebhookConfiguration is deprecated in v1.16+, unavailable in v1.22+; use admissionregistration.k8s.io/v1 ValidatingWebhookConfiguration
Error: timed out waiting for the condition
 (exit status 1)

What can I do to fix that ?

Thanks for any inputs or insights on this issue.

Cheers, Luc

FabianKramm commented 3 years ago

@lucmichalski thanks for opening this issue! As discussed in slack the helm command timed out because the containers were not up in time. The problem seems like the probes failed because the container took too long to start up. This apparanetly can happen in slow local clusters. We could think about increasing the thresholds for the probes to fix this problem.

carlmontanari commented 2 years ago

Sounds like this one has been sorted out so I'm going to go ahead and close it out! Feel free to reopen/create a new issue if folks are still experiencing this!