The anjana-k8s kit packages the official Anjana Data deployment on Kubernetes as a Helm chart (anjana-platform). It allows installing all microservices and, optionally, the in-cluster persistence layers on any compatible Kubernetes distribution. For AWS EKS environments, platform configuration can be delegated to AWS Secrets Manager; for on-premises or air-gapped environments, it operates in JDBC mode without cloud dependencies.
General information
Support
|
|
|
|---|---|
|
Compatible with |
Anjana Data 26.1 |
|
Supported Kubernetes |
1.28 – 1.35 |
|
Helm |
≥ 3.12 |
|
cert-manager |
≥ 1.14 (internal TLS mode only). Not included in the kit: it must be installed beforehand in the cluster |
Included versions
Default versions of the microservices in this kit (controlled via global.version.core in the values file):
|
Service |
Version |
|---|---|
|
horus |
6.0.0 |
|
viator |
6.0.0 |
|
zeus |
6.1.0 |
|
hermes |
6.0.0 |
|
kerno |
6.0.0 |
|
minerva |
6.0.0 |
|
portuno |
6.0.0 |
|
tot |
5.2.0 |
|
drittesta |
6.0.0 |
|
marketplace |
1.0.0 |
|
anjana-ui |
5.2.0 |
|
portuno-ui |
5.2.0 |
|
adp-mcp |
1.0.0 |
The images for the in-cluster persistence layers are detailed in the Deployment Manual, in the In-cluster Persistence section.
Included assets
|
StatefulSets - Microservices |
|
|---|---|
|
|
Config Server and coordination. 2 replicas by default |
|
Deployments - Microservices |
|
|
|
Platform microservices and front-ends |
|
StatefulSets - Persistence layers (subchart |
|
|
|
In-cluster, individually activatable. Disabled by default in cloud |
|
Deployments - Plugins (subchart |
|
|
20 |
All disabled by default. Activatable via values (see Advanced k8s, "Plugin activation") |
|
Utilities included in the kit |
|
|---|---|
|
|
Management of the encrypted credentials bundle and creation of namespace, Secrets, and TLS certificates |
|
|
Initial configuration load into |
|
|
Commented reference of all the chart's configuration options |
|
|
Grafana deployment with a preconfigured data governance dashboard |
|
|
Reference of the configuration keys expected by each service (not applied during installation; used for troubleshooting) |
Recommendations
Version control
To ensure effective control of the kit's versions and changes, using Git repositories as part of the workflow is essential.
It is recommended to version the encrypted credentials file (secrets/anjana.env.aes) and the values files (values-<env>.yaml) to be able to trace any change over time and recover from unwanted changes.
Introduction to Kubernetes
Best practices
Aside from this recommendation, several best practices can be found for using Kubernetes.