-
Notifications
You must be signed in to change notification settings - Fork 0
Home
Venkata Mutyala edited this page Apr 11, 2023
·
8 revisions
- Before you do anything with Vault, ensure all the pods are
Running
.
kubectl get pods -n glueops-core-vault
Expected output:
![image](https://user-images.githubusercontent.com/6570292/231230655-d8dfc275-9afd-4a30-9c6c-625c6636ec68.png)
- If they are in a non
Running
status such as:Pending
,Container Creating
, orCrashbackLooping
you will need to diagnosis what is wrong before you can continue.
kubectl -n glueops-core-vault port-forward svc/vault-ui 8200:8200
Since we use a self-signed SSL certificate you must run export VAULT_SKIP_VERIFY=true
otherwise you will get SSL errors.
For one or more reasons you need to unseal your vault pod(s). Just run this terraform module as if it was your first deployment and you will see something like this where it's going to destroy and add 3 resources. Don't be alarmed. This is expected:
![image](https://user-images.githubusercontent.com/6570292/231232820-9435f673-6448-4adc-82c0-69dd4950e108.png)
Just type yes
and it will run unseal across the vault cluster. Don't forget to follow the prerequisites above! Once your cluster is unsealed all pods will be 1/1 under the READY
column:
![image](https://user-images.githubusercontent.com/6570292/231233204-fda704bb-dae7-4c52-a1c1-a515374d896b.png)