search

kyma-incubator / local-kyma

Local installation on k3d cluster
14 stars 10 forks source link

Istiod got problem when installing kyma #76

Closed lanphan closed 3 years ago

lanphan commented 3 years ago

Hello, I'm new to k8s and kyma, and trying to make kyma works on my local PC. I did run command ./kyma-k3d.sh and got this problem below, would you please help me to give some advices what's problem with it?

lanphan@Lans-MacBook-Pro local-kyma % ./kyma-k3d.sh
2af08e21153c458f03cf570e88391d08a6ea95924225898f74c7f9756949af32 7bd408f3f3e78a18c418bb12d91a309eb13d3dd952d11e0a3d46a52b58a3b944 WARN[0000] No node filter specified
INFO[0000] Prep: Network
INFO[0000] Re-using existing network 'k3d-kyma' (2af08e21153c458f03cf570e88391d08a6ea95924225898f74c7f9756949af32) INFO[0000] Created volume 'k3d-kyma-images'
INFO[0001] Creating node 'k3d-kyma-server-0'
INFO[0001] Creating LoadBalancer 'k3d-kyma-serverlb'
INFO[0001] Starting cluster 'kyma'
INFO[0001] Starting servers...
INFO[0001] Starting Node 'k3d-kyma-server-0'
INFO[0008] Starting agents...
INFO[0008] Starting helpers...
INFO[0008] Starting Node 'k3d-kyma-serverlb'
INFO[0013] (Optional) Trying to get IP of the docker host and inject it into the cluster as 'host.k3d.internal' for easy access INFO[0015] Successfully added host record to /etc/hosts in 2/2 nodes and to the CoreDNS ConfigMap INFO[0015] Cluster 'kyma' created successfully!
INFO[0015] --kubeconfig-update-default=false --> sets --kubeconfig-switch-context=false INFO[0015] You can now use it like this:
kubectl config use-context k3d-kyma kubectl cluster-info Cluster created in 0 min 24 sec ✔ Istio core installed
✘ Istiod encountered an error: failed to wait for resource: resources not ready after 5m0s: timed out waiting for the condition
Deployment/istio-system/istiod
✘ Ingress gateways encountered an error: failed to wait for resource: resources not ready after 5m0s: timed out waiting for the condition
Deployment/istio-system/istio-ingressgateway

  • Pruning removed resources Error: failed to install manifests: errors occurred during operation

Thanks so much

lanphan commented 3 years ago

I did solve this issue thanks to support from my colleague. There are 2 main things need to check in order to make it works:

  1. HDD allocated to Docker in Mac (in my case, it's not enough so that it cannot pull new image to store)
  2. Timeout when deploying istio (if your Internet is so slow, default timeout is 5 minutes)