Overview
Bahriya Tersane is a catalogue of production Helm charts and operators: databases, caches, identity, a container registry, continuous integration and the workload shapes that applications are deployed with. They are the charts that run the managed services on bahriya.cloud, licensed to your organisation for installation on your own premises: infrastructure your organisation controls, including its own accounts with a cloud provider.
Everything in Tersane is installed and upgraded with Helm. Most charts run the service directly, including the failover and maintenance it needs. Where a service is best run by a Kubernetes operator, its chart installs the operator, and the operator then creates and manages each instance of the service; that chart’s documentation describes the resources you create to request one.
The charts are built for the Bahriya Kubernetes Engine and its defaults, and install on any conformant Kubernetes distribution. On a distribution other than BKE, read Running Tersane without BKE before the first installation.
Getting started
- Access and credentials: the two credentials your organisation holds, one for charts and one for images.
- Installing a chart: adding the repository and installing a release with a values file you keep.
- Upgrading a chart: moving a release to a newer chart version, and what an upgrade cannot change.
The charts
Each chart’s page documents its values, its behaviour and the decisions it makes on your behalf. Further pages cover topics such as backup and recovery.
Data
mysql: MySQL, standalone or as a highly available clusterpostgresql: PostgreSQLcloudnative-pg: CloudNativePG, the operator that runs the PostgreSQL clusters, installed once per clustervalkey: Valkey, standalone, with Sentinel, or shardedmemcached: Memcachedcouchdb: Apache CouchDB, a document databaseopensearch: OpenSearch, for search and log analytics
Messaging
Identity
keycloak: Keycloak, for identity and single sign-on
Registry and CI
harbor: Harbor, a container image and chart registryonedev: OneDev, for Git repositories with code review, issues, and container, npm and Maven registriesconcourse: Concourse, for continuous integration and delivery
Workloads
safeena(ship): Web services, with ingress, TLS and autoscalingkhadim(servant): Workers and daemonssaat(hour): Scheduled jobssipar-gateway(shield): The gateway for a cluster, installed once per cluster, with address-based access control for TCP clients and a response cache, each behind a switchsipar-route(shield): A library chart, used inside an application’s own chart and never installed on its own, that renders the application’s entry on the cluster’s Sipar gateway, with its access, rate-limit and cache policies; it needs sipar-gateway
Security
clamav: ClamAV, as a shared malware scanner in the clusteropenbao: OpenBao, for secrets managementsecrets-store-csi-driver: The Secrets Store CSI driver, which mounts secrets into Pods as files through a providerkyverno: Kyverno, for admission policypolicy-reporter: Policy Reporter, a view in the cluster of Kyverno’s policy reportstrivy-operator: Trivy Operator, for scanning the images running in the clusterlogging: Cluster logs in OpenSearch, with the Kubernetes audit log, dashboards and alerts
Convoys
A convoy is an optional addition installed on top of Tersane, for one industry or one requirement. The Compliance and Assurance Convoy is available, and its chart is documented at compliance. The Banking Convoy, the on-premises installation and upgrade of digital banking applications from specialist vendors, and the Identity Verification Convoy are coming soon. Each convoy’s documentation is published here with its release.