Prerequisites
- Kubernetes cluster v1.16+
- Helm v3.0+
Note
Before you start using Helm, configure kubeconfig.
$HOME/.kube/config apiVersion: v1 kind: Config clusters: - cluster: certificate-authority-data: <CERTIFICATE_DATA> server: <SERVER_URL> name: <CLUSTEER_NAME> contexts: - context: cluster: <CLUSTER_NAME> user: <USER_NAME> name: <CONTEXT_NAME> current-context: <CONTEXT_NAME> users: - name: <USER_NAME> user: <AUTHENTICATION_DATA>
Add the Helm repository
Execute the following command:
helm repo add acp https://charts.cloudentity.io
helm repo update
Learn more
See Helm Repo for the documentation for the command.
Add Docker Credentials
Cloudentity uses docker images from private repository. Docker credentials must be added before installing chart.
kubectl create secret docker-registry docker.cloudentity.io --docker-server=docker.cloudentity.io --docker-username=<your-name> --docker-password=<your-password>
Install Chart
Install the Helm chart with RELEASE_NAME
set to a value of your choice.
helm install RELEASE_NAME acp/kube-acp-stack
Learn more
See Helm Install for the documentation for the command.
Result
Congratulations! Your Cloudentity platform instance is now up and running! If you want, you may now move to applying Advanced Configuration or installing Additonal Dependencies.
Install Additional Dependencies
Even though your Cloudentity deployment is up and running, to get it fully working you need to install some additional dependencies:
-
Fission to be able to execute Cloudentity Extensions in a secure environment
-
TimescaleDB to be able to store Audit Events.
Fission
For instructions on how to install and configure fission, refer to the Configuring Fission to Run Functions as a Service article.
TimescaleDB
For instructions on how to install and configure TimescaleDB, refer to the Installing and Configuring TimescaleDB for Storing Audit Events article.