Skip to content
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions CHANGELOG.md
Original file line number Diff line number Diff line change
Expand Up @@ -8,6 +8,11 @@ annotation in `charts/appwrite/Chart.yaml`.

## [Unreleased]

## [2.2.0] - 2026-11-16

Appwrite 2.7.2. Upgrading from 2.1.0: see
[docs/upgrading.md](docs/upgrading.md#to-220).

### Security

- `appwrite/geo` 0.3.9, which updates libpq to 18.7 and clears the image's high PostgreSQL findings.
Expand Down
2 changes: 1 addition & 1 deletion README.md
Original file line number Diff line number Diff line change
Expand Up @@ -10,7 +10,7 @@ to production, swap each of those for a managed service, one at a time.

| | |
| --- | --- |
| Appwrite | 2.6.2 |
| Appwrite | 2.7.2 |
| Kubernetes | 1.29 or later |
| Helm | 4, or 3.18 or later |
| Chart | `oci://ghcr.io/appwrite/charts/appwrite` |
Expand Down
85 changes: 59 additions & 26 deletions charts/appwrite/Chart.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -2,11 +2,11 @@ apiVersion: v2
name: appwrite
description: Appwrite, the open-source backend platform, on Kubernetes. Deploys the API, console, realtime, workers and schedulers with optional built-in PostgreSQL, Redis and ClickHouse.
type: application
version: 2.1.0
version: 2.2.0
appVersion: "2.7.2"
kubeVersion: ">=1.29.0-0"
home: https://github.com/appwrite/helm-chart
icon: https://raw.githubusercontent.com/appwrite/appwrite/2.6.2/public/images/logos/appwrite-icon.svg
icon: https://raw.githubusercontent.com/appwrite/appwrite/2.7.2/public/images/logos/appwrite-icon.svg
sources:
- https://github.com/appwrite/helm-chart
- https://github.com/appwrite/appwrite
Expand All @@ -24,6 +24,7 @@ maintainers:
annotations:
artifacthub.io/license: BSD-3-Clause
artifacthub.io/prerelease: "false"
artifacthub.io/containsSecurityUpdates: "true"
artifacthub.io/category: database
artifacthub.io/links: |
- name: Chart source
Expand All @@ -37,40 +38,72 @@ annotations:
- name: support
url: https://github.com/appwrite/helm-chart/issues
artifacthub.io/changes: |
- kind: security
description: '`appwrite/geo` 0.3.9, which updates libpq to 18.7 and clears the image''s high PostgreSQL findings.'
- kind: security
description: '`openruntimes/executor` 1.3.4 and `appwrite/geo` 0.3.8, rebuilt on base images with patched git, which clear both images'' high findings.'
- kind: security
description: Console 1.2.176-self-hosted, `appwrite/embedding` 0.3.3, `appwrite/exiftool` 0.1.2 and `appwrite/autogravity` 0.0.12, rebuilt with patched Debian packages (and, for Autogravity, a patched Go), which clear the open critical and high findings in all four images.
- kind: security
description: ClickHouse 26.8.36, the newest patch of the 26.8 LTS line, which updates musl, zlib and OpenSSL and clears the image's high findings.
- kind: security
description: '`appwrite/geo` 0.3.7, which updates `symfony/http-client` to 7.4.23 and clears the image''s last high finding.'
- kind: security
description: '`appwrite/postgres` 0.2.1, `appwrite/browser` 0.3.13 and `openruntimes/executor` 1.3.3, rebuilt with patched packages, which clear all of the database and executor images'' critical and high findings and all but one of the browser''s. 0.2.1 adds pg_cron and preloads it with pg_stat_statements on new data directories.'
- kind: security
description: '`appwrite/embedding` 0.3.2, which clears the image''s critical findings and most of its high ones. Models now load on the first request and unload after five idle minutes, so the pod''s idle memory drops.'
- kind: security
description: Geo listens on 8080 (`GEO_PORT`) and no longer lowers the pod's unprivileged port range.
- kind: security
description: The nightly manifest scan ignores the executor's, the orchestrator Role's and the env ConfigMap's by-design findings, each scoped to that resource.
- kind: security
description: The orchestrator's jobs service and job sidecar 5.1.0, the major version on Appwrite's main branch, which clear both images' critical and high findings. 5.x gives build pods their own user namespace by default; the chart keeps them in the node's (`compute.builds.hostUsers`), as before.
- kind: security
description: '`appwrite/geo` 0.3.6, Docker 29.9.3-dind and Console 1.2.138-self-hosted, the Console tag on Appwrite''s main branch, which clear the critical findings in all three images and most of the high ones in the first two. The Console image now patches Brotli for CVE-2026-111497.'
- kind: security
description: '`openruntimes/executor` 1.3.2 and `appwrite/browser` 0.3.12, ahead of the tags in Appwrite 2.6.2''s `docker-compose.yml`, which clear most of both images'' critical and high findings.'
- kind: security
description: '`appwrite/geo` 0.3.5, which moves from `appwrite/base` 1.1.1 to 2.2.9 and clears most of the image''s critical and high findings.'
- kind: security
description: 'Appwrite 2.6.2, a security release: its base image patches Brotli for CVE-2026-111497, and it tightens API keys, realtime, GraphQL, storage, VCS and outbound requests (release notes). No schema change: the data migration is 2.6.1''s.'
links:
- name: release notes
url: https://github.com/appwrite/appwrite/releases/tag/2.6.2
- kind: security
description: Update the Console image to 1.2.108-self-hosted, the one Appwrite 2.6.2 ships, which patches DOMPurify to 3.4.17 for GHSA-cg2g-xh64-v4q7 and GHSA-mrv2-3pqr-j5jr.
- kind: security
description: 'Update the images whose base layers the nightly Trivy scan flags to their newest patch releases: Redis 7.4.12-alpine, redis_exporter v1.96.0-alpine, SeaweedFS 4.52 and Docker 29.9.2-dind. SeaweedFS 4.52 also patches go-jose to 4.1.6 for CVE-2026-116587.'
- kind: changed
description: Appwrite 2.6.1, with console 1.2.97 and the orchestrator's jobs service and job sidecar 2.2.4. The console shows the Appwrite version (`VITE_APPWRITE_VERSION`).
- kind: changed
description: 'The browser is on by default (`browser.enabled`), since Sites are: it renders their preview screenshots. Without it, every site deployment logs "Screenshot capturing failed" and the console shows no preview.'
- kind: changed
description: The API's startup probe waits for the marker Appwrite 2.6 writes once it has created its core schema, so no traffic reaches a pod that would answer 500 until then.
description: Appwrite 2.7.2 (`appVersion`), with Console 1.2.181-self-hosted. Adds the `alerts` queue (8 coroutines) in `separate` and `grouped` worker modes and the alerts scheduler in `separate` scheduler mode; the combined worker's coroutine budget goes to 83 and `screenshots` to 4, matching Appwrite. The env defaults gain 2.7's variables (realtime limits, alerts, APNs and Functions domain fallback). The migration hook runs 2.7's V25 migration on upgrade.
- kind: changed
description: The built-in PostgreSQL gets a 1Gi `/dev/shm`, up from 256Mi, as in Appwrite's Docker install.
description: The built-in ClickHouse's `init.sh` resets `table_readonly`, which ClickHouse 26.7 and later set on the system log tables they replace, before giving those tables a TTL. Without it the pod fails to start after the upgrade to 26.8, which also needs AVX2 on x86 nodes.
- kind: changed
description: The combined worker sizes its pools for 79 coroutines, up from 78, for the new `maintenance` queue.
description: The browser 0.3.8 and ExifTool 0.1.1 images, as in Appwrite 2.6.2's `docker-compose.yml`.
- kind: changed
description: CI upgrades from the published chart 2.0.0 with default values.
- kind: added
description: ExifTool, on by default (`exiftool.enabled`), which removes location, camera and capture-time metadata from images uploaded to buckets with *Image metadata* stripping on (optional-components.md).
links:
- name: optional-components.md
url: https://github.com/appwrite/helm-chart/blob/main/docs/optional-components.md#exiftool
- kind: added
description: 'The `maintenance` queue, which cleans up projects nobody used in the last 30 days: consumed by the combined worker, by `worker-maintenance` in `separate` mode, and in `grouped` mode by the group that lists it, or a `worker-maintenance` Deployment of its own when none does. With `tasks.scheduler.mode: separate`, a `scheduler-maintenance` task schedules it (architecture.md).'
description: '`_APP_MEMORY_LIMIT`, new in Appwrite 2.6.2, sets the PHP memory limit of every Appwrite process (512M, as before). Raise it, with realtime''s memory limit, for a realtime that holds thousands of connections (production.md).'
links:
- name: architecture.md
url: https://github.com/appwrite/helm-chart/blob/main/docs/architecture.md#worker-topologies
- kind: added
description: '`storage.s3.external.pathStyle` (`_APP_STORAGE_S3_PATH_STYLE`), for endpoints Appwrite 2.6 can''t tell are bucket addresses, such as a custom domain (storage.md). The built-in store always uses path-style requests.'
- name: production.md
url: https://github.com/appwrite/helm-chart/blob/main/docs/production.md#capacity
- kind: changed
description: Project SMTP, messaging SMTP providers and migration sources on a private or reserved address need it in `_APP_ALLOWED_INTERNAL_ADDRESSES` from Appwrite 2.6.2 on (networking.md). The chart's own `smtp` settings aren't affected.
links:
- name: storage.md
url: https://github.com/appwrite/helm-chart/blob/main/docs/storage.md#your-own-s3-store
- kind: added
description: Setup notes for Entire, the Git provider Appwrite 2.6 adds (integrations.md).
- name: networking.md
url: https://github.com/appwrite/helm-chart/blob/main/docs/networking.md#requests-to-private-addresses
- kind: changed
description: The console offers Entire as a Git provider (integrations.md).
links:
- name: integrations.md
url: https://github.com/appwrite/helm-chart/blob/main/docs/integrations.md#entire
- kind: changed
description: CI upgrades from the published chart 2.1.0 with default values.
- kind: added
description: Troubleshooting for site deployments whose screenshot fails.
description: The render fails when `compute.secrets.orchestratorSecret` is Appwrite's placeholder `your-secret-key`, which Appwrite 2.6.2 refuses for job callbacks, unless `compute.secrets.existingSecret` supplies the secret instead. An empty value, the default, still generates a random secret.
- kind: fixed
description: 'The weekly upstream drift check installs PHP, which the gcrunner image lacks: it found Appwrite 2.6.2 but failed before opening an issue.'
- kind: fixed
description: '`make update-images` writes quoted tags such as SeaweedFS''s `"4.48"` (it reported the bump but left the file unchanged) and runs on macOS''s bash 3.2, where an anonymous registry pull failed on an unbound variable.'
- kind: fixed
description: The `artifacthub.io/images` annotation names the built-in datastores' images after their component (`database`, `redis`, `clickhouse`, `s3`, `database-exporter`, `redis-exporter`) instead of `builtin` and `builtin-exporter`. The nightly Trivy scan uploads under these names, so the six images overwrote each other's results and alerts flapped between fixed and reopened every night.
artifacthub.io/images: |
- name: appwrite
image: docker.io/appwrite/appwrite:2.7.2
Expand Down
2 changes: 1 addition & 1 deletion charts/appwrite/README.md
Original file line number Diff line number Diff line change
@@ -1,6 +1,6 @@
# Appwrite Helm chart

![Version: 2.1.0](https://img.shields.io/badge/Version-2.1.0-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 2.7.2](https://img.shields.io/badge/AppVersion-2.7.2-informational?style=flat-square)
![Version: 2.2.0](https://img.shields.io/badge/Version-2.2.0-informational?style=flat-square) ![Type: application](https://img.shields.io/badge/Type-application-informational?style=flat-square) ![AppVersion: 2.7.2](https://img.shields.io/badge/AppVersion-2.7.2-informational?style=flat-square)

Appwrite, the open-source backend platform, on Kubernetes. Deploys the API, console, realtime, workers and schedulers with optional built-in PostgreSQL, Redis and ClickHouse.

Expand Down
4 changes: 2 additions & 2 deletions docs/gitops.md
Original file line number Diff line number Diff line change
Expand Up @@ -294,7 +294,7 @@ spec:
source:
repoURL: ghcr.io/appwrite/charts
chart: appwrite
targetRevision: 2.1.0
targetRevision: 2.2.0
helm:
valuesObject:
appwrite:
Expand Down Expand Up @@ -374,7 +374,7 @@ Things that differ from the Helm CLI:
dry run, which doesn't touch the cluster:

```console
helm install appwrite oci://ghcr.io/appwrite/charts/appwrite --version 2.1.0 \
helm install appwrite oci://ghcr.io/appwrite/charts/appwrite --version 2.2.0 \
-n appwrite -f values.yaml --dry-run=client | sed -n '/^NOTES:/,$p'
```
- **No `ignoreDifferences` needed.** With the values above, two renders are
Expand Down
4 changes: 2 additions & 2 deletions docs/migrating-from-docker.md
Original file line number Diff line number Diff line change
Expand Up @@ -5,8 +5,8 @@ keeping all data.

Before you start:

- **Same Appwrite version.** The chart deploys Appwrite 2.6.2. Upgrade the
Docker install to 2.6.2 first, including its data migration. A Docker
- **Same Appwrite version.** The chart deploys Appwrite 2.7.2. Upgrade the
Docker install to 2.7.2 first, including its data migration. A Docker
install on 2.2.0 can also move as it is: install the chart with
`--set image.tag=2.2.0` in step 3 and drop it in step 5, which then runs
the migration; give that upgrade a `--timeout` long enough for it
Expand Down
66 changes: 64 additions & 2 deletions docs/upgrading.md
Original file line number Diff line number Diff line change
Expand Up @@ -11,6 +11,7 @@ the chart upgrades Appwrite. You can pin a different Appwrite version with
| 1.0.0 | 2.3.0 |
| 2.0.0 | 2.5.0 |
| 2.1.0 | 2.6.1 |
| 2.2.0 | 2.7.2 |

The [changelog](../CHANGELOG.md) lists what changed in each chart version,
and [version notes](#version-notes) what you have to do about it.
Expand Down Expand Up @@ -53,11 +54,11 @@ the Job as soon as the manifests are applied.
for breaking API changes your apps depend on.
4. **Don't skip a data migration.** `migrate` applies only the migration of
the version it runs and doesn't replay those of the versions in between.
Several releases share a migration: every version from 1.9.6 to 2.6.2
Several releases share a migration: every version from 1.9.6 to 2.7.2
uses the same one, so 2.0 → 2.6 is a single step. 1.8 → 2.6 isn't: go to
a release from 1.9.0 to 1.9.5 first, whose migration 2.6 doesn't repeat.
The table is in Appwrite's
[`src/Appwrite/Migration/Migration.php`](https://github.com/appwrite/appwrite/blob/2.6.2/src/Appwrite/Migration/Migration.php).
[`src/Appwrite/Migration/Migration.php`](https://github.com/appwrite/appwrite/blob/2.7.2/src/Appwrite/Migration/Migration.php).

```console
helm upgrade appwrite oci://ghcr.io/appwrite/charts/appwrite \
Expand Down Expand Up @@ -183,6 +184,67 @@ and after. A release without an entry needs nothing beyond `helm upgrade`.
When you skip versions, apply the entries of every version in between,
oldest first.

### To 2.2.0

Appwrite 2.7.2. The data migration runs: 2.6 and 2.7 share a migration
class, but 2.7's adds attributes, indexes and collections, so back up first.
The built-in PostgreSQL, Redis, ClickHouse and object store restart once, on
newer images.

**Built-in ClickHouse:** 26.8 needs AVX2 on x86 nodes. On a node without it
the pod doesn't start; pin the previous image with `clickhouse.builtin.image.tag`
or move the pod to a node that has it.

**New pods.** With `workers.mode: separate`, a `worker-alerts` Deployment
joins the workers, and with `tasks.scheduler.mode: separate`, a
`scheduler-alerts` task.

**Grouped workers:** the new `alerts` queue runs in a `worker-alerts`
Deployment of its own unless a group lists it. To keep the number of pods,
add it to a group:

```yaml
workers:
groups:
core:
queues: [databases, deletes, maintenance, alerts, mails, messaging, notifications, certificates, migrations, webhooks]
```

**Executor secret:** the executor Appwrite 2.6 ran (1.1.2) let a function or
site read files from the executor container, its secret included. If anyone
you don't fully trust can deploy functions or sites, rotate
`compute.secrets.executorSecret` (or the `executor-secret` key of your own
Secret) after the upgrade.

**What Appwrite 2.7 changes** for self-hosters (release notes:
[2.6.2](https://github.com/appwrite/appwrite/releases/tag/2.6.2),
[2.7.0](https://github.com/appwrite/appwrite/releases/tag/2.7.0),
[2.7.1](https://github.com/appwrite/appwrite/releases/tag/2.7.1),
[2.7.2](https://github.com/appwrite/appwrite/releases/tag/2.7.2)):

- A realtime connection holds at most 100 subscriptions, 100 channels and
100 queries, and a user at most 32 connections per realtime pod. Raise the
first three with `_APP_LIMIT_REALTIME_SUBSCRIPTIONS`,
`_APP_LIMIT_REALTIME_CHANNELS` and `_APP_LIMIT_REALTIME_QUERIES`, set
through `appwrite.config`.
- Bulk update, upsert and delete from client sessions return 401. They need
an API key or a console user.
- An API key that creates a migration needs the write scope of every
resource it imports, and a key that configures a function or site can only
add scopes it holds itself.
- Turning MFA off needs a recent MFA challenge, and a TOTP code works once.
- Push messages a device hadn't yet received over MQTT at the time of the
upgrade aren't delivered when it reconnects.
- Project SMTP, messaging SMTP providers and migration sources on a private
or reserved address need it in `_APP_ALLOWED_INTERNAL_ADDRESSES`
([networking.md](networking.md#requests-to-private-addresses)).
- If you changed `_APP_DOMAIN_FUNCTIONS`, list the old domain in
`_APP_DOMAIN_FUNCTIONS_FALLBACK` to keep serving preview URLs on it.
- `_APP_MAINTENANCE_INTERVAL` should be a multiple of 300 seconds. The
default, 86400, is.
- The server key is versioned. Nothing changes with the default; keep
`_APP_OPENSSL_KEY_V1`.

### To 2.1.0

Appwrite 2.6.1. The data migration runs: 2.5 and 2.6 share a migration
Expand Down