Miniflux on GKE Autopilot

Miniflux is a minimalist, self-hosted RSS/Atom feed reader — a single static Go binary that stores all state in PostgreSQL. This module deploys Miniflux on GKE Autopilot on top of the App_GKE foundation, which provisions and manages the shared Google Cloud and Kubernetes infrastructure.

This guide focuses on the cloud services Miniflux uses and how to explore and operate them from the Google Cloud Console and the command line. For the mechanics that are common to every GKE application — Workload Identity, ingress, autoscaling, CI/CD, Cloud Armor, IAP, Binary Authorization, VPC Service Controls, backups, and the deployment lifecycle — refer to the App_GKE foundation guide rather than repeating them here.

What Miniflux costs on RAD, and how that compares

Running Miniflux in your own GCP project costs about $136.37/month in Google Cloud charges; RAD's module fee is a one-time 175 credits (or 157.5 credits in a RAD-managed project), covering setup and support -- not the ongoing cloud bill, which Google bills you directly in your own project or RAD meters hourly in credits in a RAD-managed one. Or see the Cloud Run guide for the alternative deployment target; either way, if you deploy into a RAD-managed project you can pause the whole thing for free when you are not using it -- see Pause it for free below.

What you pay on RAD

	Your own project	RAD-managed project
Module fee	175 credits, once	157.5 credits, once (10% lower)
Build time	metered in credits as the build runs (a few credits, typically)	same
Google Cloud running cost	~$136.37/month, billed to your own billing account at Google's list price	~105 credits/day, metered hourly by RAD at list price plus margin

Default running cost in your own project

Resource	US$/month (Google list price, us-central1)
GKE Autopilot pod, 2x vCPU / 4 GiB	$79.35
Cloud SQL for PostgreSQL, 1 vCPU / 3.75 GB, zonal, 10 GB SSD	$51.02
Cloud NAT and networking	$5.00
Cloud Storage (add-ons, backups)	$1.00
GKE cluster management fee	shared across every GKE app in the project; $0 if this is your only cluster, else ~$73
Total	$136.37

How it compares

the project's own official hosted instance costs $15/year (about $1.25/month) (source: https://miniflux.app/#pricing), run by the project itself with no infrastructure to operate -- the comparison that matters here is less the sticker price and more whether you want the vendor's own cloud or your own GCP project with RAD managing it.
Running it yourself on a bare VPS is still the cheapest cash option -- Hetzner CPX22 (2 vCPU/4GB) runs about $24/month, a DigitalOcean 2 vCPU/4GB Droplet is also $24/month, and a GCP Compute Engine e2-standard-2 (2 vCPU/8GB) is about $49/month -- plus the admin's own time for backups, security patches and upgrades, which RAD's managed Cloud SQL, Secret Manager and monitoring cover for you -- but RAD's price is never meant to beat a VPS, only to replace the admin time a VPS still needs.
Either way, this is a single-user feed reader, so the running cost above is what actually drives the bill, not the module fee -- and that running cost is the one you can pause (see below).

Pause it for free: delete a RAD-managed project, restore it when you need it

This is the headline for a RAD-managed project. Deleting a RAD-managed project first unlinks its billing, then asks Google to delete the project outright -- Google's own 30-day recoverable soft delete. Unlike deleting one module, this does not tear down Cloud SQL, any VM or the compute resource one by one: the whole project simply stops, and nothing is charged while it waits, because billing is already unlinked.

Restoring, within 30 days and only by the project's owner, asks Google to undelete the project and reattaches its billing account, then asks you to run Update on each deployment to confirm everything came back. Because nothing was individually destroyed, that Update finds the same resources already there -- it is a check, not a rebuild, and an Update never charges the module fee again. This costs only a handful of credits (under US$1) in total for a typical 2-3-deployment chain.

What this needs: you must own the project (not one RAD only manages billing for), you must restore it yourself within 30 days -- after that Google deletes it for good -- and restoring is admitted like creating a new project, so your purchased credit balance must still clear the tier's floor (100 credits for the sandbox tier most study/demo use fits). Google says most services are fully working again within 36 hours of a restore.

One real gap: nightly backups are written to a bucket inside the project, and that bucket has Cloud Storage's soft-delete explicitly turned off, so it is very likely gone as soon as you delete the project -- even though the project itself is recoverable for 30 days. If you have customised the app and want to keep that work, copy a backup out (to Google Drive, or a bucket outside the project) before deleting. For a default install with nothing irreplaceable in it, this does not matter.

Pay only while you use it, the other way: delete and redeploy

In your own project (or once you are past the 30-day restore window above), the alternative is to delete Miniflux outright and redeploy it later. A redeploy costs the module fee again, plus the builds -- roughly 175 + 3-6 credits of build time.

Deleting saves money only once Miniflux would otherwise sit unused long enough to clear that redeploy cost against its own daily running cost -- against the own-project total above, that works out to about 4 days or more. Most of the running cost here is usually the database; it stops only when nothing else in the project uses it, so deleting this app while something else shares the project saves only this app's own compute part.

Keep data first: nightly backups go to a bucket inside the deployment and are deleted with it, so copy the latest backup out before deleting if you want to keep it.

Lab sessions and Managed Environments

Lab sessions, for training: a trainer runs a session for a class. Each participant gets the app in their own Google Cloud project for 15 minutes to 24 hours, within an allowance the trainer sets. Either the trainer funds every place, or each participant pays for their own. Everything is deleted when the session ends and unused credits go back to the trainer.
Managed Environments, for consultancies: a partner runs the app for a client from a ring-fenced wallet it funds, and settles with the client directly. If the wallet runs low, billing pauses and the data is kept, so nobody receives an unexpected charge. At the end the partner hands the project over and the deployments become the client's own.
Credits can be bought in more than 20 currencies, including XAF, XOF, NGN, GHS, KES and ZAR, by card, bank transfer or mobile money.

Sources (8 October 2026): Google Cloud Billing Catalog API list prices; radmodules.dev/pricing for RAD's own fees and daily-credit estimates; https://cloud.google.com/resource-manager/docs/delete-restore-projects for the pause/restore mechanics; https://miniflux.app/#pricing for the named competitor's price.

1. Overview

Miniflux runs as a single-container Go web workload. The deployment wires together a focused set of Google Cloud services:

Capability	Google Cloud service	Notes
Compute	GKE Autopilot	Single Go binary in a Deployment, horizontally autoscaled between `min`/`max` replicas
Database	Cloud SQL for PostgreSQL 15	Required — Miniflux stores all state here; no MySQL/other engine
Object storage	Cloud Storage (none)	Miniflux needs no bucket; an optional Filestore NFS mount is available but unused by default
Cache & queue	None	Miniflux has no Redis dependency and no separate worker
Secrets	Secret Manager	Auto-generated `ADMIN_PASSWORD` (initial owner); database password
Ingress	Cloud Load Balancing	External LoadBalancer with `ClientIP` session affinity, optional custom domain + managed certificate

Sensible defaults worth knowing up front:

PostgreSQL 15 is mandatory. The database engine is fixed by the shared application layer; selecting any other engine breaks startup.
The feed poller runs in-process. Miniflux has no separate worker — the same pod serves the UI and refreshes feeds on POLLING_FREQUENCY. Keep at least one replica running so polling continues (GKE does not scale to zero).
The initial owner is seeded, not self-registered. CREATE_ADMIN = 1 seeds the admin account from the ADMIN_PASSWORD secret on first boot; open self-service signup stays off. Retrieve the password from Secret Manager to log in.
Schema migrations run on boot (RUN_MIGRATIONS = 1) — there is no separate migrate job, so upgrading the version applies schema changes automatically.
No Redis. enable_redis = false — Miniflux keeps every feed, entry, and session in PostgreSQL. Leave it off. Because there is no shared queue, running multiple replicas simply shares request load (each still polls independently).
Session affinity is ClientIP. Keeps a client pinned to one pod for a consistent UI session.
DATABASE_URL is composed at runtime by the container entrypoint (libpq keyword/value form), branching on the GKE Auth Proxy loopback (127.0.0.1, sslmode=disable) so the same image works on Cloud Run and GKE.

2. Google Cloud Services & How to Explore Them

All commands assume you have run gcloud container clusters get-credentials <cluster> --region <region> --project <project> and that PROJECT, REGION, and NAMESPACE are set. The namespace and other identifiers are reported in the deployment Outputs.

A. GKE Autopilot — the Miniflux workload

Miniflux pods run as a Deployment on Autopilot listening on port 8080, billed for the CPU/memory they request. Horizontal Pod Autoscaling sizes the deployment between the minimum and maximum replica counts.

Console: Kubernetes Engine → Workloads → select the Miniflux workload to see pods, revisions, and events. Kubernetes Engine → Services & Ingress shows the external IP.

CLI:

kubectl get pods,svc,hpa -n "$NAMESPACE"
kubectl logs -n "$NAMESPACE" deploy/<service-name> --tail=100
kubectl describe hpa -n "$NAMESPACE"          # current vs target utilisation

See App_GKE for how Autopilot, scaling, and the workload type (Deployment vs StatefulSet) are managed.

B. Cloud SQL for PostgreSQL 15

Miniflux stores all application data (feeds, entries, users, sessions, categories) in a managed Cloud SQL for PostgreSQL 15 instance. Pods reach it privately through the Cloud SQL Auth Proxy sidecar over loopback (127.0.0.1); no public IP is exposed. On first deploy the db-init Job creates the miniflux database and role and installs the hstore extension owned by the app role.

Console: SQL → select the instance for connections, backups, flags, metrics.

CLI:

gcloud sql instances list --project "$PROJECT"
gcloud sql instances describe <instance-name> --project "$PROJECT"
# Open an interactive shell to inspect schema/data:
gcloud sql connect <instance-name> --user=miniflux --database=miniflux --project "$PROJECT"

The instance name, database, user, and password secret are surfaced in the Outputs. For the connection model, automated backups, and password rotation, see App_GKE.

C. Cloud Storage / NFS

Miniflux needs no object storage — it keeps all state in PostgreSQL, so no data bucket is provisioned by the application layer. The optional Cloud Filestore mount (enable_nfs, at /opt/miniflux/storage) is off by default, because Miniflux never writes to it.

Console: Filestore → Instances (if NFS is enabled); Cloud Storage → Buckets.

CLI:

gcloud filestore instances list --project "$PROJECT"
gcloud storage buckets list --project "$PROJECT"

See App_GKE for CMEK options and GCS Fuse mounts.

D. Secret Manager

One secret is generated automatically: ADMIN_PASSWORD — the initial owner password seeded into Miniflux on first boot. The database password is managed separately by the foundation.

Console: Security → Secret Manager.

CLI:

gcloud secrets list --project "$PROJECT" --filter="name~miniflux"
gcloud secrets versions access latest --secret=<secret-name> --project "$PROJECT"

The database password secret name is in the Outputs. See App_GKE for the Secret Store CSI integration and rotation.

E. Networking & ingress

By default the workload is exposed through an external Cloud Load Balancing IP with ClientIP session affinity. A custom domain with a Google-managed certificate can be enabled, and a static IP can be reserved so the address survives redeploys. When a custom domain is used, set BASE_URL so Miniflux emits correct absolute links.

Console: Network services → Load balancing; VPC network → IP addresses.

CLI:

kubectl get ingress,svc -n "$NAMESPACE"
gcloud compute addresses list --project "$PROJECT"

See App_GKE for custom domains, Cloud CDN, and static IP details.

F. Cloud Logging & Monitoring

Pod stdout/stderr flow to Cloud Logging; GKE and Cloud SQL metrics flow to Cloud Monitoring. Optional uptime checks and alert policies are available. The entrypoint logs its DATABASE_URL connection mode at start — useful when diagnosing DB connectivity.

Console: Logging → Logs Explorer; Monitoring → Dashboards / Alerting.

CLI:

gcloud logging read 'resource.type="k8s_container" AND resource.labels.namespace_name="'"$NAMESPACE"'"' \
  --project "$PROJECT" --limit 50

3. Miniflux Application Behaviour

First-deploy database setup. The db-init Job runs db-init.sh using postgres:15-alpine. It connects through the Cloud SQL Auth Proxy and idempotently creates the miniflux database and role, grants privileges, re-owns the public schema, and installs the hstore extension owned by the app role (so Miniflux migration v119, which drops hstore, succeeds). The job then posts to the proxy sidecar's /quitquitquit so the Job pod completes; it is safe to re-run.
Schema migrations on boot. The entrypoint sets RUN_MIGRATIONS=1, so Miniflux applies its own schema migrations on every start — no separate migrate step. Allow extra time on the first boot for the initial schema build.
Initial owner is seeded. CREATE_ADMIN=1 seeds the admin account (ADMIN_USERNAME) from the ADMIN_PASSWORD secret. It is idempotent — later boots log "user already exists". Retrieve the password to log in:
```
gcloud secrets versions access latest \
  --secret=secret-<resource-prefix>-miniflux-admin-password --project "$PROJECT"
```
Health path. This module's startup and liveness probes default to HTTP / (the login page, an unauthenticated 200 OK). Miniflux also serves an unauthenticated 200 OK at /healthcheck if you prefer a dedicated probe path. Do not point probes at authenticated pages.
The feed poller is in-process. Feeds refresh on POLLING_FREQUENCY inside each pod. Keep min_instance_count >= 1 so polling runs; extra replicas each poll independently (there is no shared queue to coordinate them).
BASE_URL drives absolute links. It defaults to the injected internal service URL; set it explicitly (via environment_variables) to the external LoadBalancer or custom-domain URL once the address is known.

Inspect the db-init job and pods:

kubectl get jobs -n "$NAMESPACE"
kubectl logs -n "$NAMESPACE" job/<job-name>

4. Configuration Variables

Variables are grouped exactly as they appear on the deployment platform. Only settings specific to or notable for Miniflux are listed; every other input is inherited from App_GKE with its standard behaviour and defaults.