keep maintain one instance of vault

after the data between `vault` and `vault-nci`, the old vault is going to decommission, the new `vault-nci` becomes `vault`. After the change user can only see the instance `vault`, that would be simple for the later maintenance. Signed-off-by: Bin Ju <[email protected]>
concourse · Jan 9, 2020 · 3caac2a · 3caac2a
1 parent 0aa902d
commit 3caac2a
Showing 1 changed file with 4 additions and 6 deletions.
diff --git a/deployments/with-creds/vault/README.md b/deployments/with-creds/vault/README.md
@@ -2,14 +2,12 @@
 
 1. ~Clone [vault-helm](https://github.com/hashicorp/vault-helm) into charts/vault-helm and checkout the version referenced in `requirements.yaml`~
 1. We have a forked version of [vault-helm](https://github.com/concourse/vault-helm). Which has something special for the postgres backend. Please keep using this version until it gets merged back to `vault-helm` chart.
-1. `vault-nci` and `vault` are alive at the same time so far. `vault` may decommission in the future after `vault-nci` is all set.
-1. How to deploy `vault-nci`
+1. How to deploy `vault`
     1. `git clone https://github.com/concourse/vault-helm` to the `charts` (hush-house/deployments/with-creds/vault/charts) directory.
-    1 `ln -s vault vault-nci` 
-    1. `make creds-vault-nci`
-    1. `make deploy-vault-nci`. If you get the error `app-name has no deployed releases`, delete the deployment with the command `helm delete --purge vault-nci --tls`, then try again.
+    1. `make creds-vault`
+    1. `make deploy-vault`. If you get the error `app-name has no deployed releases`, delete the deployment with the command `helm delete --purge vault --tls`, then try again.
 1. Verify
-    1. You should be able to login in to the container with the command `kubectl exec -it -n vault-nci vault-nci-0 /bin/sh`
+    1. You should be able to login in to the container with the command `kubectl exec -it -n vault vault-0 /bin/sh`
     1. `export VAULT_SKIP_VERIFY=true`
     1. `vault status`.
         ```