Skip to content
zeabur-ossPublic

Latest commit

 

History

145 Commits

Folders and files

NameName
Last commit message
Last commit date
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

Zeabur: deploy like a PaaS, get standard Kubernetes; the review of a new service lists a Deployment, a Service and an Ingress with their YAML before it creates them

Zeabur

Simple, secure deployments on your own Kubernetes.

Zeabur is an open-source platform you host yourself. It runs in your cluster (or on your machine), shows the cluster as projects and services, explains what is wrong in plain words, and lets you change things safely. It works with the objects you already have, never acts with more rights than you have, and keeps no state of its own: no database, no custom resources.

oss.zeabur.com/zeabur shows what Zeabur does, and the documentation covers installing, deploying, configuring and operating the cluster, and leaving Zeabur, in English, 繁體中文 and 简体中文.

Status: pre-alpha. The API may still change, and it has been tried on few clusters. Do not point it at a cluster you cannot afford to break.

Home: what needs you across the cluster, grouped by where each problem comes from
What needs you, across every project, grouped by where each problem comes from.
A project as a map of its services, databases and the connections between them
One page per project: a map or a list, with what needs attention and what happened.
A service that keeps crashing: why, in plain words, and what to do
Diagnoses in plain words, with what to do and the evidence.
A service rolling out, with its usage and a domain that the browser can't reach
Rollouts, usage and domains: progress, CPU and memory against the limits, and whether each domain answers.
A PostgreSQL database: its state, a warning about one instance with no backups, and how to connect
Databases with their connection details and a warning when nothing would take over.
The cluster: an end-of-life Kubernetes version and nodes running out of memory and disk
The cluster: Kubernetes support dates, node pressure, backups, notifications and components.

Screenshots of the built-in demo data (cargo run -p zeabur-api --example demo), taken by scripts/docs-shots.sh docs/readme-shots.yaml.

Get started

Releases lists what a release contains and how to verify it.

Build from source

In the Nix dev shell, which provides every tool:

git clone https://github.com/zeabur-oss/zeabur && cd zeabur
nix develop
./scripts/build-ui.sh
ZEABUR_UI_DIST="$PWD/web/dist" cargo build --release --locked -p zeaburctl
./target/release/zeaburctl ui                  # --context <name> for another context

zeaburctl ui listens on a random loopback port, opens the browser, and makes every request with your current kubeconfig context.

Contributing

License and credits

Apache-2.0. Contributions are accepted under the Developer Certificate of Origin.

Third-party content in this repository:

  • Zeabur Catalog, embedded from its release bundle at the commit in flake.lock (Apache-2.0).
  • Kubernetes' release schedule in crates/zeabur-catalog/src/versions.rs, from kubernetes/website data/releases (CC BY 4.0, The Kubernetes Authors).
  • Rendered manifests of upstream Helm charts in fixtures/charts, test input only, each under its chart's license (Apache-2.0 or MIT; listed in fixtures/charts/README.md).

The web interface is built with @zeabur-oss/design-system (Apache-2.0), which contains shadcn/ui's components, theme and base styles (MIT), the Inter and JetBrains Mono fonts (SIL Open Font License 1.1) and the Zeabur logo; its README lists their notices. The built interface, embedded in the binary and the image, includes those fonts and the logo.

The container image includes Mozilla's CA certificate bundle as packaged by nixpkgs (MPL-2.0).

Releases

Packages

Used by

Contributors

Languages