CODEWITHSUNDEEP
kubernetes-helmistio
Dean Schulze
Dean Schulze

Reputation: 10303

istioctl install fails with multiple timeouts

Following the istio docs to install the demo profile I get the errors below. Others have been getting this error for months with no resolution.

Do other installation methods work? The helm installation has been deprecated, but does it still work? Is there a way to remove the partial installation that I have now?

$ istioctl install --set profile=demo
Detected that your cluster does not support third party JWT authentication. Falling back to less secure first party JWT. See https://istio.io/docs/ops/best-practices/security/#configure-third-party-service-account-tokens for details.
✔ Istio core installed                                                                                                                      
  Processing resources for Istiod. Waiting for Deployment/istio-system/istiod                                                               
✘ Istiod encountered an error: failed to wait for resource: resources not ready after 5m0s: timed out waiting for the condition             
Deployment/istio-system/istiod
✘ Egress gateways encountered an error: failed to wait for resource: resources not ready after 5m0s: timed out waiting for the conditions...
Deployment/istio-system/istio-egressgateway
✘ 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

Upvotes: 3

Views: 12159

Answers (2)

Nazar Ostapchuk
Nazar Ostapchuk

Reputation: 31

I had the same problem. I set profile and it helped

istioctl install --set profile=minimal

Upvotes: 0

Dean Schulze
Dean Schulze

Reputation: 10303

I tried the istioctl install on a different kubernetes cluster that has 32 GB RAM on the master and it succeeded. This cluster was created the same way as the first one with 12 GB RAM on the master so the difference that allowed the install to work is the amount of RAM.

There is a minimum RAM requirement for istioctl install that is not documented and needs to be. The timeout error message is misleading. It should say insufficient RAM. There should also be a document for bare metal installs.

The preflight check should not indictate pass if there is not sufficient RAM to do the install.

I hope this helps someone else who runs into the timeout messages.

Upvotes: 13

Related Questions