Skip to content

Latest commit

 

History

History
93 lines (67 loc) · 2.25 KB

README.md

File metadata and controls

93 lines (67 loc) · 2.25 KB

Provision the environment

For this lab we will use a Kubernetes-based Vault environment that reflects the following diagram:

Prerequisites

Having completed labs:

Minikube

Start Minikube

$ minikube start --kubernetes-version='v1.25.3'
😄   minikube v1.28.0 on Darwin 13.1 (arm64)
... 
🏄  Done! kubectl is now configured to use "minikube" cluster and "default" namespace by default

Check Minikube status

$ minikube status
minikube
type: Control Plane
host: Running
kubelet: Running
apiserver: Running
kubeconfig: Configured
$ kubectl get nodes
NAME       STATUS   ROLES           AGE   VERSION
minikube   Ready    control-plane   22s   v1.25.3

Vault

Install Vault

$ helm repo add hashicorp https://helm.releases.hashicorp.com
"hashicorp" has been added to your repositories
$ helm repo update
Hang tight while we grab the latest from your chart repositories...
...Successfully got an update from the "hashicorp" chart repository
Update Complete. ⎈Happy Helming!⎈
$ helm install vault hashicorp/vault --set "server.dev.enabled=false" --namespace vault --create-namespace --version v0.23.0 --values vault-values.yaml
NAME: vault
LAST DEPLOYED: Sat Mar 19 01:03:03 2022
NAMESPACE: vault
STATUS: deployed
REVISION: 1
NOTES:
Thank you for installing HashiCorp Vault!

Now that you have deployed Vault, you should look over the docs on using
Vault with Kubernetes available here:

https://www.vaultproject.io/docs/


Your release is named vault. To learn more about the release, try:

  $ helm status vault
  $ helm get manifest vault

Check the installation

$ kubectl get pods -n vault
NAME                                   READY   STATUS    NAME                                    READY   STATUS    RESTARTS   AGE
vault-0                                 0/1     Running   0          9m54s
vault-agent-injector-59b9c84fd8-zvqxb   1/1     Running   0          9m55s