The catalogue
Every chart in Tersane.
The charts that run the managed services on bahriya.cloud, grouped by what they provide. Software with an upstream name keeps it, so you know what you are running; the charts Mamluk designed for deploying your own applications carry Arabic names.
Data
- mysql MySQL, standalone or as a highly available clusterDocumentation
- postgresql PostgreSQL
- valkey Valkey, standalone, with Sentinel, or shardedDocumentation
- memcached MemcachedDocumentation
- 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
- safeenaship Web services, with ingress, TLS and autoscalingDocumentation
- khadimservant Workers and daemonsDocumentation
- saathour Scheduled jobsDocumentation
Security
- clamav ClamAV, as a shared malware scanner in the clusterDocumentation
- 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
How the charts are made
Defaults decided for production.
Each chart carries the values bahriya.cloud runs, and each default is a decision you can read and override in a values file you keep. Among them:
- Requests and limits on every container. In the data and workload charts, init containers, sidecars and test pods included, so a release does not fail against a namespace quota.
- Spread across nodes. Replicas are spread across nodes wherever the cluster allows, so the loss of one node does not take a service with it.
- Disruption budgets. A PodDisruptionBudget by default for long-running workloads and caches, so a node drain cannot remove every replica at once.
- Network policy for the data charts. MySQL and Valkey are reachable from their own namespace by default, and from elsewhere only where your values say so.
- Backups and recovery built in. MySQL and Valkey back up to S3-compatible storage when backups are enabled, and their documentation sets out the restore, including point-in-time recovery for MySQL.
Each chart's documentation sets out its defaults in full.
Industry-specific additions, such as the Banking Convoy, are described under Convoys.