Skip to content

Commit 61a3378

Browse files
committed
doc improvements
1 parent 6208a89 commit 61a3378

File tree

1 file changed

+8
-6
lines changed

1 file changed

+8
-6
lines changed

documentation/01-Deployment-CDK-Sunbirdrc2.md

Lines changed: 8 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -126,12 +126,8 @@ The stack `sunbirdrc2helmStacksbrc2` installs the Sunbird RC 2.0 services' helm
126126

127127
It is recommended to review the [Deployment through Helm](02-Deployment-Helm-Sunbirdrc2.md) guide to become familiar with Sunbird RC 2.0 Helm charts.
128128

129-
Follow the post installation steps to start using Sunbird RC 2.0 services
130-
131-
* [Post Installation Procedure](03-Post-Installation-Procedure.md)
132-
133-
* NOTE:
134-
If Vault becomes sealed, you have the option to unseal it using the unseal token stored in Kubernetes secrets.
129+
*** NOTE: Optional***
130+
The Vault Init job ensures Vault is unseald post installation. However if you find out Vault becomes sealed, you have the option to unseal it using the unseal token stored in Kubernetes secrets.
135131

136132
```
137133
kubectl get secrets vault-unseal-key -n <namespace>
@@ -141,7 +137,13 @@ Unseal the vault pods using below command.
141137
```
142138
kubectl exec <vault_pod_name> -n <namespace> -- vault operator unseal <vault_unseal_key>
143139
```
140+
141+
Follow the post installation steps to start using Sunbird RC 2.0 services
142+
143+
* [Post Installation Procedure](03-Post-Installation-Procedure.md)
144+
144145
**Lastly, if you wish to clean up, run 'AWS CDK destroy' to remove all AWS resources that were created by it.**
145146
```
146147
cdk destroy [STACKS..]
148+
cdk destroy --all
147149
```

0 commit comments

Comments
 (0)