With BKE
A cluster from BKE. A platform from Tersane.
The Bahriya Kubernetes Engine makes two decisions: the network fabric and the Kubernetes version. Tersane supplies what runs above them. Together they are the combination that runs bahriya.cloud, assembled from parts you can name, version and keep.
The cluster
Bahriya Kubernetes Engine
Upstream Kubernetes, pinned to an exact patch, with Calico as its network fabric. Every other component (ingress, storage, certificates and the rest) is chosen per cluster, one line each, and installed and upgraded by BKE.
bke.bahriya.cloudThe platform
Bahriya Tersane
Production charts for the services applications depend on: databases, caches, identity, a container registry, continuous integration, and the workload shapes your own applications are deployed with.
The catalogueHow they fit
The charts are built on BKE's defaults.
Tersane's charts assume the components BKE installs, so on a BKE cluster they install as documented, with no defaults to change. Calico, BKE's network fabric, is always present; enable the components the charts you use depend on:
| BKE component | Used by |
|---|---|
| Calico (always present) | The network policy of mysql, valkey and memcached |
| Longhorn | The volumes of mysql and valkey, and MySQL's volume encryption and snapshots |
| Kong | safeena, and external access to mysql and valkey |
| cert-manager | Certificates for safeena and the MySQL web client |
Tersane can also be licensed on its own, for any conformant Kubernetes distribution, at a higher price. Running Tersane without BKE sets out what to supply instead.
Try BKE
A 14-day BKE trial licence is issued self-service from the Mamluk console, with no sales call and no payment details, and installs exactly the distribution a paid licence does.
Start a 14-day BKE trialLicensing both
BKE is licensed per cluster and Tersane per organisation. To discuss licensing the two together, contact Mamluk.
Enquire about a licence