Bahriya Tersane

Bahriya Tersane · ter-SAH-neh

Production Helm charts for the platform above your cluster.

Databases, caches, identity, a container registry and continuous integration, packaged as the charts that run bahriya.cloud and licensed for installation on your own premises. They are built for the Bahriya Kubernetes Engine and its defaults, and install on any conformant Kubernetes distribution.

Read the documentation Enquire about a licence

On your premises

The charts install inside your perimeter. No data leaves it.

The charts we run

The same charts operate the managed services on bahriya.cloud.

One licence per organisation

Not per cluster, node or core. Supported from within the GCC.

The catalogue

Every capability a platform needs, as a chart you can read.

Data

  • mysql · MySQL, standalone or as a highly available cluster
  • postgresql · PostgreSQL
  • valkey · Valkey, standalone, with Sentinel, or sharded
  • memcached · Memcached
  • couchdb · Apache CouchDB, a document database
  • opensearch · OpenSearch, for search and log analytics
  • velero · Velero, for backing up and restoring cluster resources and volumesUnder consideration

Messaging

  • rabbitmq · RabbitMQ, a message broker
  • kafka · Apache Kafka, for event streaming

Identity

  • keycloak · Keycloak, for identity and single sign-on

Registry and CI

  • harbor · Harbor, a container image and chart registry
  • onedev · OneDev, for source control, build pipelines, and container, npm and Maven registries
  • concourse · Concourse, for continuous integration and delivery

Workloads

  • safeena (ship) · Web services, with ingress, TLS and autoscaling
  • khadim (servant) · Workers and daemons
  • saat (hour) · Scheduled jobs

Security

  • clamav · ClamAV, as a shared malware scanner in the cluster
  • openbao · OpenBao, for secrets management
  • kyverno · Kyverno, for admission policyUnder consideration
  • gatekeeper · OPA Gatekeeper, for admission policyUnder consideration
  • trivy-operator · Trivy Operator, for scanning the images running in the clusterUnder consideration

Each chart is documented in full: its values, its upgrade path and the decisions it makes on your behalf. Browse the chart documentation

Convoys

Industry-specific additions to Tersane.

A convoy is an optional addition that carries the applications and configuration one industry needs. It installs on top of Tersane and is licensed separately.

Tersane Banking Convoy

A curated catalogue of digital banking applications, built and maintained by our banking specialists and installed alongside your bank's existing digital banking platform.

Read about the Banking Convoy

The Bahriya Kubernetes Engine decides the network fabric and the Kubernetes version. Tersane supplies what runs above them.

Together they are the combination that runs bahriya.cloud: a platform assembled from parts you can name, version and keep.

Tersane may also be licensed on its own, for any conformant Kubernetes distribution. The charts ship with the Bahriya Kubernetes Engine's defaults, so running them elsewhere calls for experience with Kubernetes and the components the charts expect, or for Mamluk's engineering services.

About the Bahriya Kubernetes Engine Running Tersane without BKE

The name

A tersane was a naval arsenal, the yard in which a fleet was built and fitted. The Ottoman word came from the Ligurian tersaná, and before that from the Arabic dār aṣ-ṣināʿa, the house of industry. English took arsenal from the same root.

Licensing

Tersane is licensed per organisation, per year, with the Bahriya Kubernetes Engine or on its own. Pricing is provided on request.

Enquire about a licence