After changing the install job name in !137 (merged) , I noticed that the new install job was being created for already-installed sites. This is dangerous!
Initialized condition before ensuring the install job.false even if the operator simply failed to exec into the pod, which is unintended. Instead, it should be Unknown.