Virtru Private Keystore: Deployment via Helm
Pulling the helm chart
To get started with your helm chart, create a local directory to store your chart. Then run the following command to add Virtru's helm charts to your local helm repo:
helm repo add virtru-charts https://virtru-corp.github.io/virtru-charts/
To view your helm repos, run:
helm repo list
You should see
virtru-charts added from the URL
To download a chart for editing, run the following command:
helm pull virtru-charts/cks --untar
You should see a directory called
cks created inside of your working directory.
There are a number of ways that Kubernetes secrets can be managed. If you do not have an existing external secret manager for your Kubernetes clusters, you can create secrets by using the
appSecrets section of the
Please note we recommend that you consider using an external secrets manager. Creating secrets via the
values.yaml is a default option to help get your CKS up and running more quickly.
This section will detail potential changes that you will need to make to your
To serve traffic appropriately, you must have an ingress controller for your CKS service. This is enabled by default, but you will need to update the host under
ingress.hosts.host to match the FQDN of your CKS.
Depending on your environment, you will need to add annotations to:
- Apply your CA signed certificate
- Designate load balancer configurations
- Expose your load balancer to the internet
Update your secrets to match the values from your local CKS config as mapped below.
|Filename||Value from CKS setup script|
You can have multiple RSA keypairs on your CKS as long as they follow the naming convention rsa###.pub and rsa###.pem for all public/private keypairs.
Note: Indentation matters for a multiline string, ensure proper indentation for your CKS keys secrets.
Virtru Private KeystoreInstalling the
Use a standard helm install command to deploy your CKS. An example command is listed below:
helm install -n virtru -f ./values.yaml cks ./ --create-namespace