Varnish Helm Chart 1.8.4
This is a patch release for the Varnish Helm Charts.
This is a patch release for the Varnish Helm Charts.
This is a patch release for the Varnish Helm Charts.
varnish-otel now supports using a Prometheus exporter via OTEL_METRICS_EXPORTER=prometheus. Metrics are exposed on an HTTP /metrics endpoint for Prometheus to scrape.
This is a patch release for the Varnish Helm Charts.
News recently surfaced about a new HTTP/2 denial-of-service technique dubbed the “HTTP/2 Bomb”, reported to affect a number of HTTP/2 implementations including Envoy, Apache httpd, nginx, Microsoft …
This is a minor release for the Varnish Helm Charts.
The current release of our Varnish container images is the last one that will ship with the telegraf binary included. Starting with the next release, telegraf will no longer be present in the images.
See Varnish Controller Changelog for more details on the changes and the upgrade notes for more details on how to upgrade.
See Broadcaster Changelog page for more details.
See Varnish Controller Changelog for more details on the changes and the upgrade notes for more details on how to upgrade.
varnish-otel is now compatible with Varnish Cache >= 9.0.1. Note that tracing will still require vmod-otel, which is a Varnish Enterprise feature, but metrics and logging will work without extra …
This is a patch release for the Varnish Controller Helm Charts.
See Broadcaster Changelog page for more details.
See Varnish Controller Changelog for more details on the changes and the upgrade notes for more details on how to upgrade.
This is a patch release for the Varnish Helm Charts.
See Varnish Controller Changelog for more details on the changes and the upgrade notes for more details on how to upgrade.
This is a patch release for the Varnish Helm Charts.
See Varnish Controller Changelog for more details on the changes and the upgrade notes for more details on how to upgrade.
See Varnish Controller Changelog for more details on the changes and the upgrade notes for more details on how to upgrade.
This is a patch release for the Varnish Helm Chart.
See Varnish Controller Changelog for more details on the changes and the upgrade notes for more details on how to upgrade.
This is a patch release for the Varnish Helm Chart.
This is a patch release for the Varnish Helm Charts.
This is a patch release for the Varnish Helm Chart.
See Varnish Controller Changelog for more details on the changes and the upgrade notes for more details on how to upgrade.
After installing this upgrade, make sure to start Brainz before the Router. More details are in the upgrade notes.
This version focuses on finer logging, introducing new environment variables that will impact the internal use of varnishlog-json and varnishncsa.
Bugfix release to correct a crash at startup introduced by 1.6.0.
This is a release for Varnish Helm Chart.
See Varnish Controller Changelog for more details on the changes and the upgrade notes for more details on how to upgrade.
See Varnish Controller Changelog for more details on the changes and the upgrade notes for more details on how to upgrade.
Maintenance release, including:
See Varnish Controller Changelog for more details on the changes and the upgrade notes for more details on how to upgrade.
This is a patch release for Varnish Helm Chart.
See Varnish Controller Changelog for more details on the changes and the upgrade notes for more details on how to upgrade.
Varnish Enterprise running on Debian Bookworm with openssl/3.0.17-1~deb12u1 installed is affected by a bug in this specific version of OpenSSL. The Docker images provided by Varnish Software are built …
See Varnish Controller Changelog for more details on the changes and the upgrade notes for more details on how to upgrade.
See Varnish Controller Changelog for more details on the changes and the upgrade notes for more details on how to upgrade.
With the release of Varnish Enterprise 6.0.14r6, we are streamlining access to Licensed Add-ons – advanced modules that extend Varnish beyond core Content Delivery use cases.
See Varnish Controller Changelog for more details on the changes and the upgrade notes for more details on how to upgrade.
See Varnish Controller Changelog for more details on the changes and the upgrade notes for more details on how to upgrade.
See Varnish Controller Changelog for more details on the changes and the upgrade notes for more details on how to upgrade.
See Varnish Controller Changelog for more details on the changes and the upgrade notes for more details on how to upgrade.
This release comes with a lot of breaking changes due to major changes to the deployment and file handling. Please see upgrade notes to see important changes. As a result of these major changes, the …
Note: We suggest upgrading all components with this patch release.
The latest versions of our container images are now based on Debian bookworm and continues to be updated daily with the latest OS updates.
Note: Only router requires update with this patch release.
This is a patch release.
Note: Only api-gw requires update with this patch release.
Note: We recommend updating all components for this patch release, as they all include fixes. See: versioning.
Note: We recommend updating all components for this patch release, as they all include fixes. See: versioning.
Note: Only nats, router and api-gw requires upgrading for this patch release, see versioning.
Update the Golang crypto library due to CVE-2024-45337. While Varnish Controller does not use the affected part of this library, this ensures we build with the latest version.
Note: Only brainz needs upgrading for this patch release, see versioning.
Note: All components needs to be upgraded for this release, see versioning.
This is a patch release for Varnish Helm Chart.
Note: All components needs to be upgraded for this release, see versioning.
This is a patch release for Varnish Helm Chart.
This is a patch release for Varnish Helm Chart.
This is a patch release for Varnish Controller with the following fixes:
Note: All components needs to be upgraded for this release, see versioning.
This is a minor release for Varnish Helm Chart.
This is a patch release for Varnish Controller with the following fixes:
This is a patch release for Varnish Controller with the following fixes:
Note: All components needs to be upgraded for this release, see versioning.
Note: All components needs to be upgraded for this release, see versioning.
This is a patch release.
This is a minor release for varnish-enterprise with the following changes:
This is a patch release for Varnish Controller with the following fixes:
If certificates are used within the controller, the controller must be updated before updating varnish to version 6.0.13 or above.
If certificates are used within the controller, the controller must be updated before updating varnish to version 6.0.13 or above.
Note: Only the agent and the UI are affected by this release, see versioning.
Note: All components needs to be upgraded for this release, see versioning.
This is a minor release for varnish-enterprise with the following changes:
Today news surfaced about a new HTTP/2 vulnerability affecting a large number of HTTP/2 implementations.
This is a patch release for Varnish Controller with the following fixes:
This is a patch release for Varnish Controller with the following fixes:
This is a major release of Varnish Controller and all its components need to be updated. The release contains several non backward compatible changes. These changes are described in the upgrade …
This is a patch release for Varnish Controller with the following fixes:
This is a patch release for Varnish Controller with the following fixes:
Note: All components needs to be upgraded for this release, see versioning.
A base64 decoding vulnerability has been discovered in vmod-digest.
This is a patch release for Varnish Controller with the following fixes:
This is a patch release for Varnish Controller with the following fixes:
This is a patch release for Varnish Controller with the following fixes:
Note: All components needs to be upgraded for this release, see versioning.
This is a patch release for Varnish Controller with the following fixes:
This is a patch release for Varnish Controller with the following fixes:
This is a patch release for Varnish Controller with the following fixes:
This is a patch release for Varnish Controller with the following fixes:
Note: All components needs to be upgraded for this release, see versioning.
Maintenance release, including:\
The latest versions of our container images are now based on Debian bullseye and will from now on be updated daily with the latest OS updates.
A request forgery attack can be performed on Varnish Cache and Varnish Cache Plus servers that have the HTTP/2 protocol turned on. An attacker may introduce characters through the HTTP/2 …
Note: This issue applies only to the open source version of Varnish Cache, in version 7.0.x, 7.1.x and 7.2.x. Varnish Enterprise is not affected. For more information please see the open source …
This is a patch release of Varnish Controller.
This is a patch release of Varnish Controller.
This is a minor release. It includes bug fixes, improvements and some new features.
This is a major release of Varnish Controller and all its components need to be updated. The release contains several non backward compatible changes. These changes are described in the upgrade …
Note: This issue applies only to the open source version of Varnish Cache, in version 7.0.x and 7.1.x. Varnish Enterprise is not affected. For more information please see the open source project’s …
Maintenance release, including AWS SDK version upgrade.
This is a patch release for Varnish Controller with the following fixes:
This is a patch release for Varnish Controller with the following fixes:
This is a patch release for Varnish Controller with the following fixes:
Note: All components needs to be upgraded for this release, see versioning.
The release includes a bug fix in the API-GW.
See Broadcaster Changelog page for more details.
“Maintenance release, including dependency updates. No changes are required by the user”
This release is NOT backward compatible with 3.0. All Varnish Controller components requires an upgrade.
A request smuggling attack can be performed on HTTP/1 connections on Varnish Cache and Varnish Enterprise servers. The smuggled request would be treated as an additional request by the Varnish server, …
Important: If you are not running 4.1.9r1 (released November 30th 2017) or newer, make sure you read the associated information on upgrading to 4.1.9r1 before you upgrade to 4.1.11r7.
Important: If you are not running 4.1.9r1 (released November 30th 2017) or newer, make sure you read the associated information on upgrading to 4.1.9r1 before you upgrade to 4.1.11r6.
This is a patch release for Varnish Controller with the following fixes:
Updated December 15, 2021.
This is a patch release for Varnish Controller with the following fixes:
This is a patch release for Varnish Controller with the following fixes:
This release is NOT backward compatible with 2.0.5. All Varnish Controller components requires an upgrade.
This is a patch release that optimizes statistics inserts into the database, lowering CPU usage of Brainz. It also normalizes dynamic backends statistic counters for the vmod-goto. Meaning that stored …
This is a patch release that includes a fix for growing snapshots database table and fixes a panic in brainz.
See Broadcaster Changelog page for more details.
This is a patch release that includes a couple minor bug fixes and improvements.
This is a patch release that includes several minor bug fixes and improvements.
This is a patch release that includes several minor bug fixes and improvements.
This release is NOT backward compatible with 1.0.4. All Varnish Controller components requires an upgrade.
This release includes several bug fixes.
This release includes several bug fixes and also some new backward compatible additions.
This release introduces two changes that help set up update-reload pipeline:
A license file is now required. The license file is added to brainz. Please contact sales or support to retrieve a license file. The system will continue running without a license file, but login is …
See Varnish Controller Documentation page for more details.
The full set of changes can be found on the changelog. We recommend you to upgrade to this release.
See Broadcaster Changelog page for more details.
See Broadcaster Changelog page for more details.
This release fixes a rare timeout issue that could occur at high load.
This version is recommended for all users.
This release adds the -confwatch switch to reload configuration file automatically if it changes.
This version is recommended for all users.
The full set of changes can be found on the changelog. We recommend you to upgrade to this release.
The biggest item of this release is the support for the Azure platform, but it also simplifies the AWS setup by automatically trying to find the AWS configuration file from the user name.
This is a patch release to fix an issue with TLS automatic server name verification.
This Varnish Broadcaster release addresses some known issues and adds some new functionality.
This version is recommended for all users.
This is a minor release with updated boot.vcl. The packaging for boot.vcl has been updated as well.
This release now supports loading of TLS certificates that are owned by root.
This update fixes several issues and also adds some new functionality.
This Varnish Broadcaster release addresses some known issues and adds some new functionalities.
Important: If you are not running 4.1.9r1 (released November 30th 2017) or newer, make sure you read the associated information on upgrading to 4.1.9r1 before you upgrade to 4.1.11r5.
This version is recommended for all users.
This update is recommended for all users.
This update is recommended for all users.
This update is recommended for all users.
The full set of changes can be found on the changelog. We recommend you to upgrade to this release.
The full set of changes can be found on the changelog. We recommend you to upgrade to this release.
This Varnish Broadcaster release addresses a minor issue in regards with relaxing the parsing of the group names. It is now possible to include dashes and underscores in the group names.
This update is recommended for all users.
This version is recommended for all users.
This Varnish Broadcaster release addresses some known issues and adds some new functionalities.
Important: If you are not running 4.1.9r1 (released November 30th 2017) or newer, make sure you read the associated information on upgrading to 4.1.9r1 before you upgrade to 4.1.11r3.
Important: If you are not running 4.1.9r1 (released November 30th 2017) or newer, make sure you read the associated information on upgrading to 4.1.9r1 before you upgrade to 4.1.11r3.
Add an option to extend the format of the nodes.conf file.
Important: If you are not running 4.1.9r1 (released November 30th 2017) or newer, make sure you read the associated information on upgrading to 4.1.9r1 before you upgrade to 4.1.11r2.
This Varnish Administration Console (VAC) patch release fixes Purger bug concerning client SocketTimeouts.
This update is recommended for all users.
Important: If you are not running 4.1.9r1 (released November 30th 2017) or newer, make sure you read the associated information on upgrading to 4.1.9r1 before you upgrade to 4.1.11r1.
Important: If you are not running 4.1.9r1 (released November 30th) or newer, make sure you read the associated information on upgrading to 4.1.9r1 before you upgrade to 4.1.10r6.
This is purely a feature release, adding support to AWS autoscaling groups.
This update is recommended for all users.
This Varnish Broadcaster release addresses some known issues and adds some new functionalities.
The full set of changes can be found on the changelog. We recommend you to upgrade to this release.
This release addresses a bug in the Kubernetes module causing a out-of-bound exception and crashing discovery. It also fixes two pain points in case of misconfiguration:
This Varnish Agent release addresses some known issues and adds some new functionalities.
This Varnish Administration Console (VAC) release fixes some minor UI bugs, adds a feature to enable ReadOnly user to view VCL and Parameter sets and introduces MongoClient connection string.
Important: If you are not running 4.1.9r1 (released November 30th) or newer, make sure you read the associated information on upgrading to 4.1.9r1 before you upgrade to 4.1.10r5.
Important: We have added a new configuration file /opt/vac/etc/logback.xml and made some changes in the /opt/vac/etc/log4j.xml, /opt/vac/etc/defaults and service unit file to introduce proper logging …
Due to a bug in certain libcurl versions, VHA can push HTTPS replications requests to the wrong nodes in the cluster, leaving others untouched. This version works around the issue by closing the …
Varnish Administration Console (VAC) 3.7.0 has been updated to offer better user experiences to our customers. It is now fully responsive and has some various improvements to create a more modern look …
Important: If you are not running 4.1.9r1 (released November 30th) or newer, make sure you read the associated information on upgrading to 4.1.9r1 before you upgrade to 4.1.10r4.
Important: If you are not running 4.1.9r1 (released November 30th) or newer, make sure you read the associated information on upgrading to 4.1.9r1 before you upgrade to 4.1.10r3.
Important: If you are not running 4.1.9r1 (released November 30th) or newer, make sure you read the associated information on upgrading to 4.1.9r1 before you upgrade to 4.1.10r2.
This Varnish Administration Console (VAC) release fixes a purger bug where socket connections were not soaked across multiple requests.
This Varnish Administration Console (VAC) release fixes a purger bug where multiple requests on the same connection were not handled.
Important: If you are not running 4.1.9r1 (released November 30th) or newer, make sure you read the associated information on upgrading to 4.1.9r1 before you upgrade to 4.1.9r3.
The full set of changes can be found on the changelog. We recommend you to upgrade to this release.
This Varnish Administration Console (VAC) release addresses some known issues and adds some new functionalities.
Important: If you are not running 4.1.9r1 (released November 30th) or newer, make sure you read the associated information on upgrading to 4.1.9r1 before you upgrade to 4.1.9r3.
This release addresses an issue arising during VSL peak traffic, where the logger needs to prematurely flush transactions to keep track of things. This has been mitigated in version 2.1.4 by dropping …
In the 2.1 series, due to a VSL parsing error, when an ESI subrequest containing an Accept-Encoding header is replicated, all headers are discarded and the Host header is set to the node IP. The …
This revision release increase compatibility with VCL hashing the Accept headers. Before, VHA automatically added an Accept header if none was present, which would cause replication issues for request …
Today we release a new tool: Varnish Discovery. It aims to streamline VHA’s configuration by automatically producing the nodes.conf file that it needs, making HA setups using VAC or Kubernetes super …
Important: If you are not running 4.1.9r1 now (released November 30th), make sure you read the associated information on upgrading to 4.1.9r1 before you upgrade to 4.1.9r2.
This VCS release addresses several issues that where present in 4.1.4.
This VHA release builds on the 2.1.0 that notably brought request body replication, replication prevention and header addition from the VCL. The biggest change with this version is the way ESI …
This release increments the VMOD ABI version number, which means that VMODs will have to be recompiled in order to load. Packages for Varnish Cache Plus 4.1.9r1 and updated VMOD packages are available …