Difference between revisions of "StarlingX/Containers/Applications/app-vault"
< StarlingX | Containers | Applications
(→Building) |
(→Testing) |
||
| Line 9: | Line 9: | ||
== Testing == | == Testing == | ||
| − | + | Vault sanity should typically include: | |
| + | * application lifecycle: upload, apply, remove, abort, delete, and update | ||
| + | * Vault with replicas=1 (AIO-SX) and replicas=3 (AIO-DX + worker or standard controller) | ||
| + | * Configure vault with CLI and REST API | ||
| + | * Workflow for applications that are Vault aware (REST API) and unaware (vault injector) | ||
| + | * Pod recovery | ||
| + | * Vault backup and restore | ||
| + | * Vault-manager features including: rekey, PVC conversion (upgrade) | ||
| + | * Download images from private registry; network isolation test | ||
Revision as of 21:32, 28 August 2024
Application: vault-armada-app
Source
Building
- From the Debian Build environment:
VAULT_PKGS="python3-k8sapp-vault,vault-helm,vault-manager-helm,stx-vault-helm" build-pkgs -c -p $VAULT
Testing
Vault sanity should typically include: * application lifecycle: upload, apply, remove, abort, delete, and update * Vault with replicas=1 (AIO-SX) and replicas=3 (AIO-DX + worker or standard controller) * Configure vault with CLI and REST API * Workflow for applications that are Vault aware (REST API) and unaware (vault injector) * Pod recovery * Vault backup and restore * Vault-manager features including: rekey, PVC conversion (upgrade) * Download images from private registry; network isolation test
