openshift-ansible-istio-installer complete, but no pods started about openshift-ansible HOT 5 CLOSED

Actually, the job does not complete. The event describes:

Error creating: Internal error occurred: failed calling admission webhook "sidecar-injector.istio.io": Post https://istio-sidecar-injector.istio-system.svc:443/inject?timeout=30s: service "istio-sidecar-injector" not found

from openshift-ansible.

Can you please explain what you mean by complete? The installer job starts other deployments however it will finish before those are deployed, especially if any images need to be downloaded.

from openshift-ansible.

@knrc, all that is meant by 'complete' is that the installer runs and then after some minutes is no longer present (i.e. the installer pod is in Running state for some time, and then no longer exists).

Example of the symptom:
$ oc project
Using project "istio-system" on server ":8443".
$ oc get jobs
NAME DESIRED SUCCESSFUL AGE
openshift-ansible-istio-installer-job 1 0 47m
$ oc get pods
No resources found.

from openshift-ansible.

@mattmahoneyrh What state were the other deployments in? These would finish after the job since they are async.

from openshift-ansible.

I've updated the installer so the webhook is not called for pods in the istio-system namespace, this removes the confusion with @tvieira's comment referencing the webhook from a previous installation and should allow you to see the other pods while they are pulling their images.

from openshift-ansible.