ensure the init job is created as a helm hook so the chart can be upgraded

[JorritSalverda]

fixes #45

[JorritSalverda]

Hi @JuanLeon1 @DuskEagle any chance this can be approved, merged and released in the next version?

[DuskEagle]

LGTM if you could update the Chart.yaml version as mentioned in Contributing.md. Thank you!

[jonasbadstuebner]

Are you sure this works on first install as well?
Because it will not create the hook necessary for init, until after the installation would complete, which it doesn't if you handle it like this.

[prafull01]

Are you sure this works on first install as well? Because it will not create the hook necessary for init, until after the installation would complete, which it doesn't if you handle it like this.

Hi @jonasbadstuebner
It would work on the first install as well, however if you are using --wait, then post install hook doesn't get triggered and in that case it fails.
If you are not using --wait, then yes your statefulset gets created first, your crdb pods will not come up until post install hook gets completed and after that cockroachdb pod comes up properly.

[jonasbadstuebner]

My proposed solution (even though it is not rebased) is here: #450
I would have the job be deployed in parallel on install in every case, so the wait flag does not matter.