starlingx/vault-armada-app
Code Issues Proposed changes

set images to pull from configured registries

Browse Source 
Add yaml to the fluxcd manifest which is compatible with the platform's
image pull and service parameter registry override handling.  The
platform will pull the image and populate registry.local, and the vault
injector agent will pull from registry.local.

Story: 2010393
Task: 47927

Test Plan:
PASS: sysinv.log shows that agentImage image is pulled when vault
      server image is hardcoded differently
PASS: agent image pulls when public network is blocked
PASS: agent image pulls when it is different than vault server image
PASS: vault app test, including vault un-aware application

Change-Id: Idd1215744bb31881127a6be23cf570166c79fad8
Signed-off-by: Michel Thebeau <michel.thebeau@windriver.com>
This commit is contained in:
Michel Thebeau
2023-05-02 12:39:29 -04:00
parent 1dab2dbf8f
commit 198f4e5164
3 changed files with 42 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
stx-vault-helm/stx-vault-helm/fluxcd-manifests/vault/vault-static-overrides.yaml
View File

@@ -28,7 +28,15 @@ injector:
repository: hashicorp/vault-k8s
tag: 0.14.2
agentImage:
repository: hashicorp/vault
# Add yaml compatible with starlingx platform image pull, and
# service-parameter registry overrides. This will pull from
# private or public registry into registry.local. docker.io
# registry is assumed when omitted:
image:
repository: hashicorp/vault
tag: 1.9.2
# Set the vault yaml to refer to registry.local pulled as above
repository: registry.local:9001/docker.io/hashicorp/vault
tag: 1.9.2
tolerations: |
- key: "node-role.kubernetes.io/master"