e2e: use full-qualified-image-name for vault-init-job

On occasion deploying Vault fails. It seems the vault-init-job batch job
does not use a full-qualified-image-name for the "vault" container.

Signed-off-by: Niels de Vos <ndevos@redhat.com>
(cherry picked from commit 1845f2b77d)
This commit is contained in:
Niels de Vos 2020-11-30 10:12:38 +01:00 committed by Madhu Rajanna
parent 1fd09d8637
commit e0881258f8

View File

@ -121,7 +121,7 @@ spec:
name: init-scripts name: init-scripts
containers: containers:
- name: vault-init-job - name: vault-init-job
image: vault image: docker.io/library/vault:latest
volumeMounts: volumeMounts:
- mountPath: /init-scripts - mountPath: /init-scripts
name: init-scripts-volume name: init-scripts-volume