»Vault Enterprise License Management
You can use this Helm chart to deploy Vault Enterprise by following a few extra steps around licensing.
Note: As of Vault Enterprise 1.8, the license must be specified via HCL configuration or environment variables on startup, unless the Vault cluster was created with an older Vault version and the license was stored, or the Vault Enterprise binary has the license baked in (prem or pro version tags). More information is available in the Vault Enterprise License docs.
»Vault Enterprise 1.8+
First create a Kubernetes secret using the contents of your license file. For example, the following commands create a secret with the name vault-ent-license and key license:
Note: If you cannot find your .hclic file, please contact your sales team or Technical Account Manager.
In your chart overrides, set the values of server.image to one of the enterprise release tags. Also set the name of the secret you just created in server.enterpriseLicense.
Now run helm install:
Once the cluster is initialized and unsealed, you may check the license status using the vault license get command:
»Vault Enterprise prior to 1.8
In your chart overrides, set the values of server.image to one of the enterprise release tags. Install the chart, and initialize and unseal vault as described in Running Vault.
After Vault has been initialized and unsealed, setup a port-forward tunnel to the Vault Enterprise cluster:
Next, in a separate terminal, create a payload.json file that contains the license key like this example:
Finally, using curl, apply the license key to the Vault API:
To verify that the license installation worked correctly, using curl, run the following:
