Install Nitride
Install Nitride and securely integrate it into your environment, ensuring that workloads are verifiably trusted before granting access.
To interact with Nitride you need to install vHSM, and vHSM CLI.
Installing vHSM
You can install vHSM using, a Docker image, Helm chart, or by compiling from source.
Pull the latest image.
docker pull harbor.enclaive.cloud/vhsm/vhsm:latestSet your enterprise license key as an environment variable.
export ENCLAIVE_LICENCE=<licence-key>Start a Docker container named
vhsm-container.docker run -d --name vhsm-container -p 8200:8200 -p 8201:8201 -e ENCLAIVE_LICENCE="$ENCLAIVE_LICENCE" harbor.enclaive.cloud/vhsm/vhsm:latestVerify the container is running
docker psCheck the logs to get the environment variables, unseal key, and root token.
docker logs vhsm-containerExample Output:
WARNING! dev mode is enabled! In this mode, vHSM runs entirely in-memory and starts unsealed with a single unseal key. The root token is already authenticated to the CLI, so you can immediately begin using Vault. You may need to set the following environment variables: export VAULT_ADDR='http://0.0.0.0:8200' The unseal key and root token are displayed below in case you want to seal/unseal the vHSM or re-authenticate. Unseal Key: pafYkq2uEVve3FW7n7RM6JUK/MWEHzAxvrEdlrb4QD4= Root Token: hvs.7oXsG8t8L198HEpB865FdpFG Development mode should NOT be used in production installations!Set the environment variables as displayed in the output for accessing vHSM and save the unseal key and root token — you'll need them to access the vHSM UI or vHSM using the CLI. For more information see, vHSM login.
Access the vHSM UI.
Open your browser and go to: http://127.0.0.1:8200
Set your enterprise license key as an environment variable.
Install vHSM in your Kubernetes cluster.
Example Output:
Check if the pods are running.
Example Output:
Check if the services are running.
Example Output:
Port forward the service to access vHSM UI.
Access the vHSM UI.
Open your browser and go to: http://127.0.0.1:8200
Note: The vHSM is not initialized and unsealed by default. You will be prompted to initialize and unseal it. For more information about using the CLI , see vhsm operator.
To initialize vHSM:
To unseal vHSM. Ensure that you replace
<unseal-key>with the unseal key that you obtained after initializing the vHSM.
Prerequisites
Ensure the following are installed and configured:
Go, with the
GOPATHenvironment variable setGit, available in your system's PATH
Set the enterprise license key:
Create directory structure in your GOPATH.
Clone the vHSM repository.
Navigate into the repository.
Bootstrap the project.
Build vHSM.
To build with the UI. The
dev-uitarget only adds a build tag to include the UI if it has already been built. To include the UI, runmake static-distormake static-dist-devbefore building the main binary.Check if vHSM is installed.
If
vhsmis not found, add it to your PATH:To start vHSM server in dev mode use:
vhsm server -dev -dev-root-token-id="root"
Note: To start the server in Production mode, ensure that you have the config.json file and use the command: vhsm server -config=/etc/vault/config.json
To Access the vHSM UI. Open your browser and go to: http://127.0.0.1:8200
Next Step
Continue to install a CLI.
Last updated
Was this helpful?