From 1845f2b77d3eb3bb6a619ded4ec8dae4ccd34403 Mon Sep 17 00:00:00 2001 From: Niels de Vos Date: Mon, 30 Nov 2020 10:12:38 +0100 Subject: [PATCH] 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 --- examples/kms/vault/vault.yaml | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/examples/kms/vault/vault.yaml b/examples/kms/vault/vault.yaml index 1da9e4123..a38a835a5 100644 --- a/examples/kms/vault/vault.yaml +++ b/examples/kms/vault/vault.yaml @@ -125,7 +125,7 @@ spec: name: init-scripts containers: - name: vault-init-job - image: vault + image: docker.io/library/vault:latest volumeMounts: - mountPath: /init-scripts name: init-scripts-volume