Ron Stone cf66f5d279 Armada Deprecation and Replacement

First pass - generic updates only. (command input/output to be done)
Address patchset 1 review comments.
Replace examples using openstack with metrics server
Remove DS app from application-list output
Additional migration to FluxCD (snmp, auditd)
Minor textual change.
Fix merge conflict.
Revert install r5 change.

Story: 2009138
Task: 45238

Signed-off-by: Ron Stone <ronald.stone@windriver.com>
Change-Id: Ia40ff45f12ec7b7ffa859e0d8bb5535303870d83

2022-06-29 10:40:56 -04:00

1.6 KiB

Raw Blame History

Install Vault

Vault is packaged as a system application and is managed using system application, and system helm-override commands.

Note

Vault requires a storage backend with PVC enabled (for example, Ceph).

To install Vault, use the following procedure:

Locate the Vault tarball in /usr/local/share/applications/helm.

For example, /usr/local/share/applications/helm/vault-1.0-30.tgz.

Upload Vault, using the following command:

$ system application-upload ``/usr/local/share/applications/helm/vault-1.0-30.tgz``

Verify the Vault tarball has been uploaded.
```
$ system application-list
```
Apply the Vault application.
```
$ system application-apply vault
```
Monitor the status.
```
$ watch -n 5 system application-list
```
or
```
$ watch kubectl get pods -n vault
```
It takes a few minutes for all the pods to start and for Vault-manager to initialize the cluster.

The default configuration for the installed Vault application is:

Vault-manager

Runs as a statefulset, replica count of 1

Vault-agent-injector

Runs as a deployment, replica count of 1

Vault

Runs as statefulset, replica count is 1 on systems with fewer than 3 nodes, replica count is 3 on systems with 3 or more nodes

For more information, see Configure Vault <configure-vault>.

1.6 KiB Raw Blame History

Install Vault

1.6 KiB

Raw Blame History