Improvements
- Reduced build startup latency
- Minor fixes and improvements
Security
- Upgraded dependencies and applied security patches
Kubernetes Support
- AKS, EKS and GKE v1.35+ supported
Stay up to date with the latest features, improvements, and fixes in Pergola.
Fine grained settings to control who and how users access your applications. Configurable per stage, enables custom domains, authentication, firewall, and multiple entry points (ingresses) per component.
Define networking and tailored routing for your application:

Plug-in authentication via your prefered OIDC/OAuth provider without touching the code:

Custom domains, multiple ingress rules, and much more:

See Ingresses Documentation for details.
For scheduled jobs you can now specify a time zone. Especially useful when running jobs that depend on dailight saving time (DST) or other local time regulations.
components:
- name: "runs-daily-at-2am-german-time"
scheduled: "0 2 * * *"
scheduled-timezone: "Europe/Berlin"
See Scheduling for details.
First released as a preview feature in v1.4.3, is now GA.
The Release Webhook notifies an external service before and after each deployment. The before deployment message can be approved or rejected by the external service, enabling custom rules and quality gates before each release. The after deployment message is a notification only, e.g. for external auditing, or triggering additional workflows.
Please talk to your Pergola administrator for integration options.
Native support for Webhook events from GitLab, i.e. push events.
Improved the build process by eliminating redundant image creation.
Previously, when multiple components referenced the same Dockerfile with identical parameters, they were built independently.
Outposts now report their local version to the cluster

Minor fixes and improvements, dependency upgrades
Webhook implementations can pre-review and eventually approve or reject releases, enabling custom rules and checks before each release.
⚠️ This is a pre-release (beta) feature.
This release brings end-to-end automation, full-stage backups, and real-time visibility into what your projects cost.
Real-time usage cost tracking across all your projects, with drill-down per stage, down to per component and the consumed resources (CPU, memory, …). See the cost control documentation for details.
![]()
Back up all persistent data for a complete stage and restore it at any time. See the backups documentation for details.

See our Automated CI/CD tutorial for details.


Manage access keys for use on the CLI in scenarios like scheduled (unattended) scripts or batch scripts triggered by external systems. See the access keys documentation for details.

Manually start and stop components. See the components reference for details.

You can now inject build-related metadata variables as build-args into your Docker build:
docker:
file: Dockerfile
build-args:
- name: BUILD
value: "$(BUILD_NAME)"
- name: BUILT_WHEN
value: "$(BUILD_TS)"
- name: COMMIT
value: "$(GIT_COMMIT_ID)"
- name: BRANCH
value: "$(GIT_BRANCH)"
See the project manifest reference for more details.
Two new backend flags (both disabled by default) give platform admins stronger runtime hardening:
A security- and observability-focused release, with first-class vulnerability scanning surfaced right where you work.
Every build is automatically scanned, adding a layer of quality control before deploying a new release:

Most container images run as root (UID 0), which is a security concern. You can now explicitly run a component as a non-root user, if supported by your image:
components:
- name: web
docker:
file: Dockerfile
user: 1001
When a user is specified, Pergola applies additional security policies to further protect your application’s runtime environment.
Build and run your components on ARM64, AMD64 (default), or both, if your image and its packages support it:
components:
- name: website
docker:
file: Dockerfile
platform:
- arch: amd64
- arch: arm64
Pergola ensures your component builds and runs based on the architecture actually available in your cluster. Builds are rejected if your manifest requires an architecture the cluster does not provide.
A build is usually triggered after a few code changes — you can now see exactly what changed compared to the previous build on the same branch.

When a component fails, logs were previously the only source of information. You now get additional context on the potential root cause — particularly helpful when a component could not start at all and no application logs are available.

Custom links to external documents or services, fully configurable per customer

Prometheus metrics for Pergola admins, visualisable in tools like Grafana (a starter set of metrics, with more to come)

Configurable log retention: build logs and project-level logs are retained for a configurable period and then automatically deleted.
Deploying to a suspended stage is now supported (experimental) — use with caution, as behaviour may change in future versions
And more UX improvements and fixes
A big release that extends Pergola beyond the cluster, keeps you informed, and makes deletions reversible.
Deploy to remote environments, edge devices and IoT infrastructure:

A central hub that collects and pushes notifications about your project’s background processes while you were away or waiting:


Deleted projects and stages are archived first for a configurable period before they are ultimately deleted


While archived, a project or stage can be restored at any time without losing data or configuration

Delete unused configurations

Copy existing configurations to other stages and projects


Manage project ownership — easily assign or revoke ownership to other members

Dedicated Nodes – Configurable assignment of workloads to a specific set of nodes:
Workload Identities – Link a component to a Cloud IAM at runtime, enabling IAM-backed access to cloud resources.
This release makes deploying faster and gives you more insight into what’s actually running.
Deploy a new release directly from a build or from the configuration page


Display relevant stage status right on the project page

Suspending a stage now requires a user confirmation

command and args on components.git suffix blocking the project setup dialogMinor fixes and improvements.
Minor fixes and improvements.
Minor fixes and improvements.
Minor fixes and improvements.
Minor fixes and improvements.
Minor fixes and improvements.
Minor fixes and improvements.
Build, deploy and run your containerised applications in the cloud — without managing the cloud.

