Install standalone istio 1.67 failed by failed to wait for resource: resources not ready after 5m0s: timed out waiting for the condition

$ snap list microk8s
Name      Version  Rev   Tracking     Publisher   Notes
microk8s  v1.18.6  1584  latest/edge  canonical✓  classic

Brand new micok8s install, istio addon was initially enabled (version 1.51). But I disabled it afterward, because I would like to install the latest version 1.6.7 from the binary. https://istio.io/latest/docs/setup/getting-started/#download

$ ./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                                                                                             
✘ 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 conditionem...
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 conditiont...
Deployment/istio-system/istio-ingressgateway
✘ Addons encountered an error: failed to wait for resource: resources not ready after 5m0s: timed out waiting for the conditionnt/istio-sy...
Deployment/istio-system/grafana
Deployment/istio-system/istio-tracing
Deployment/istio-system/kiali
Deployment/istio-system/prometheus
- Pruning removed resources                                                                                                                  Error: failed to apply manifests: errors occurred during operation

Surprisingly, microk8s status now shows istio as enabled.

QUESTION: what was the resource that istio was waiting for? Where can I get more info about the installation failure? More importantly, is there a solution to fix this resource issue? So that I can attempt to re-install istio again.

Microk8s checks for a running pod named pod/istio and determined whether istio is enabled or not.
You will need dns to be enabled in the cluster.
Regarding the status reported by istioctl, you may need to check the pods created by istio.

I am facing the same issue. I am using kind, and this behavior is pretty evident in the latest releases of istio too. Do we have to allocate any extra memory for the kind cluster?