Zeabur Catalogv1
What a cluster needs, installed once in CI first.
Zeabur Catalog lists cluster components and app templates. Each entry says which chart, which version, which values, and why. CI installs and tests every one of them.
Components and templates, as data any tool can read.
- components
Components
Ingress, certificates, metrics, database operators: what a cluster gets once, with separate advice for one node and for several.
- templates
Templates
Apps such as n8n, Dify and WordPress, installed into one namespace. Images are pinned, requests and limits set, and each says how it scales and how its data is backed up.
- bundle
One signed bundle
Each release publishes one. Any tool can read it to generate helm install commands, Flux or Argo CD manifests, or k3s HelmChart objects.
Write the choice down, release it once it passes.
Write it down
One file per capability and upstream, such as components/ingress/traefik.yaml, with the chart, version, values and the reason.
Test in CI
CI installs and tests every component and template, and records idle memory and CPU.
Release
One signed bundle. Zeabur reads it to suggest what a cluster is missing, and never installs anything itself.
Some of the components
| Capability | Upstream | Single node | Multi-node |
|---|---|---|---|
| ingress | Traefik | Recommended | Recommended |
| certificates | cert-manager | Recommended | Recommended |
| metrics | VictoriaMetrics, metrics-server | Recommended | Recommended |
| logs | VictoriaLogs | Recommended | Recommended |
| volume-backup | K8up, Velero | Optional | Optional |
| event-autoscaling | KEDA | Optional | Recommended |
| replicated-storage | Longhorn | Optional | Recommended |
| databases | CloudNativePG, MariaDB Operator, MOCO | Optional | Optional |
Read one component file
Every component looks like this: why it is recommended, its licence, the capabilities it needs, and the chart and version to install.
apiVersion: catalog.zeabur.com/v1
kind: Component
metadata:
name: cert-manager
description: >
cert-manager is the standard Kubernetes certificate controller (CNCF
graduated). Its issuers live in the cluster, so it renews certificates
itself.
license: Apache-2.0
homepage: https://cert-manager.io
maturity: cncf-graduated
defaults:
single-node: recommended
multi-node: recommended
# Gateway API CRDs come with ingress; the controller exits without them.
requires: [ingress]
releases:
- name: cert-manager
namespace: cert-manager
chart: oci://quay.io/jetstack/charts/cert-manager
version: v1.21.2
...