The Cloudentity platform can be deployed on Kubernetes (K8s) using Helm and its Charts.
K8s is a container or a microservice platform that makes it possible to orchestrate computing, networking, and storage of infrastructure workloads. Helm is a package manager for K8s. It uses a packaging format called charts. A chart is a collection of files that describe a related set of resources stored on K8s. It collects manifest files and Docker addresses. You can use Helm charts to deploy Cloudentity with all its backend architecture.
You may notice that some of our naming contains a term Authorization Control Plane or ACP. It is a name for our platform that we used before rebranding our product and it still visible within customer deployed Cloudentity platform.
Cloudentity on K8s is provided with the following charts:
Cloudentity (ACP) (Standalone version)
acp-cd (declaratively manage configuration of Cloudentity data)
kube-acp-stack (including subcharts for Redis and CockroachDB)
Cloudentity Open Banking (the collection of Cloudentity Open Banking applications that provides an easy-to-operate end-to-end K8s cluster)
While working with charts, there are two most important files:
Chart.yamlwhere you can check the top-level metadata of the chart
values.yamlwhich contains a structured list of default values for the Cloudentity configuration that gets mapped to the chart template that references it (a template for the Cloudentity configuration).
Values stored in the
values.yamlfile are defaults. You can override them by invoking command
helm upgradeand specifying the
By default, the ACP Helm chart installs additional dependent charts:
- cockroachdb configuration
- redis-cluster configuration
See Helm Dependency for the documentation for the command.