Versions and support
What 0.0.1 supports
| Component | Supported | Tested with |
|---|---|---|
| PostgreSQL | 18 (18.4 in this release) | 18.4 |
| Kubernetes | 1.29 or later | 1.33 |
| cert-manager | 1.x with a CA, Vault or private PKI issuer | 1.18 and 1.21 |
| Object storage | Amazon S3, Google Cloud Storage, Azure Blob Storage, S3-compatible stores with conditional writes | Amazon S3 API (MinIO), local emulators |
| Architectures | linux/amd64 and linux/arm64 images | arm64 and amd64 |
| Install profiles | aws (EKS), gcp (GKE), azure (AKS), kubernetes (any conformant cluster) | Local Kubernetes; see known-limitations.md |
| Console sign-in | WorkOS | WorkOS |
| CLI and agent server | Linux amd64 and arm64; macOS arm64 when published |
PostgreSQL 18 is the only major version in 0.0.1. The installer refuses others, and the console offers only the majors a region lists. Later releases may add majors; a project never changes its major in place.
PostgreSQL 18.4 is built from upstream source with four small patches: a
pluggable storage manager, a hook to rebuild a single page from WAL, a call
that lets the storage manager complete PostgreSQL’s asynchronous reads with
pages it fetched itself, checksums verified as usual, and relation size
functions such as pg_relation_size that ask the storage manager. The image includes pgvector
0.8. Extensions that need superuser or server file access are not available to
your roles.
Release versions
Releases use semantic versions, MAJOR.MINOR.PATCH:
- Patch releases fix defects and security issues. They never change storage formats or remove fields, and can be rolled back to the previous patch of the same minor unless their notes say otherwise.
- Minor releases add features. Their notes state any one-way storage format change and any console schema change that limits rollback.
- Major releases may remove deprecated behaviour, announced at least one minor release in advance.
Every release is published at https://skeladb.com/releases/<version>/ with
signed images, checksums and notes. Images are always referenced by digest, so an
installation never changes without an explicit upgrade.
Compatibility promises
- The platform API and the console API are the supported interfaces. Fields may be added; existing fields are not renamed or removed within a major version.
- The Branch Kubernetes resource (
branches.skeladb.io/v1alpha1) is for operators. Fields may be added and validation may tighten between releases, but fields are never renamed or removed and stored objects stay readable. An incompatible change will arrive as a new version served besidev1alpha1for at least one minor release, with stored objects migrated by the controller. - The controller and the PostgreSQL image of one release go together; mixing releases is refused before any data is touched.
- PostgreSQL behaviour is upstream PostgreSQL 18 behaviour, with the differences listed in known-limitations.md.
Support window
Each minor release receives patch releases, including security fixes, until six months after the next minor release is published. Upgrade within that window. Support terms, response times and channels for paid licenses are set in your agreement; free-license users get community support and security fixes through the same releases.
Security
Report vulnerabilities to security@skeladb.com (see
https://skeladb.com/security#report). Fixes ship as patch releases and are
described in the release notes.