Helm chart will never succeed when `helm install` is run with `--atomic` flag set

When `helm install --set storage.persistentVolume.size="25Gi" my-cockroachdb cockroachdb/cockroachdb --version 10.0.0 --atomic` is run, the Helm chart install will never succeed and hang until timeout is exceeded, at which point the chart uninstalls. It appears at least the `cockroachdb-init` Job is never run (but I believe this extends to the 2 other cert Jobs) with `--atomic` but does run without. This pod is critical to setting the cluster up for the first time. Possibly related to #39.

Jira issue: HELM-24

Reproduce the documented helm install command with --atomic, then inspect the cockroachdb-init Job and the two certificate Jobs, comparing their behavior with a non-atomic install. Trace how the chart handles these Jobs during an atomic release; done means the installation completes successfully and the required initialization and certificate Jobs run.

Written by the indexing model from the issue text.