SearchFor readability, the following thematically groups the packages by sections:
| Varnish Cache Plus |
Varnish Broadcaster |
Varnish Discovery |
Varnish Custom Statistics |
Varnish Controller |
Varnish Router |
|||
|---|---|---|---|---|---|---|---|---|
| RHEL/Rocky/Alma 9 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ||
| RHEL/Rocky/Alma 8 | ✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ||
| RHEL/CentOS 7 | ✔¹ | ✔ | ✔ | ✔ | ✔ | ✔ | ||
| Ubuntu 22.04 (jammy) |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ||
| Ubuntu 20.04 (focal) |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ||
| Ubuntu 18.04 (bionic) |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ||
| Ubuntu 16.04 (xenial) |
✔² | ✔ | ✔ | ✔ | ✔ | ✔ | ||
| Docker (Debian bullseye) |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ||
| Debian 12 (bookworm) |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ||
| Debian 11 (bullseye) |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ||
| Debian 10 (buster) |
✔ | ✔ | ✔ | ✔ | ✔ | ✔ | ||
| Debian 9 (stretch) |
✔ | ✔ | ✔ | ✔ | ✔ | ✔³ |
¹ Without built-in TLS and with reduced performance on backend TLS using OpenSSL 1.0. For client side TLS it is necessary to use Hitch.
² Without Memory Governor.
³ Debian 9 (stretch) is not maintained any longer. We only support it for existing installations.
Packages inside the repositories are signed using this key:
2048R/4DEDD7217877 98C0 22A6 CE30 F148 7292 2E7D ED34 4DED D721This section lists the packages available in the Varnish Enterprise repositories. Some packages are add-ons to the regular subscriptions and are not available in the default repositories, in which cases it will be specified.
All packages assume you have already followed the installation instructions for the main repository, since all packages will depend on it.
Packages names are the same across all distributions.
This is the main package containing the actual Varnish Enterprise binary, with most other packages relying in on it. It comes with a large selection of essential vmods.
Some vmods require external dependencies (mmdb, sqlite3, etc.) and are
isolated here to keep the footprint of varnish-plus minimal with few dependencies.
This package includes Hitch, a TLS terminator, which is useful in cases where in-process TLS cannot be used, such as on the RHEL 7.x OS. More info is here.
Varnish High Availability, both the deprecated legacy version and the current one live in this package.
While not a hard dependency, you will most probably need to install
varnish-broadcaster along with it. If Varnish lives in a dynamic cluster,
you will also need varnish-plus-discovery
This is an add-on.
This package contains the VCL and vmod used to synchronize Varnish and Akamai configurations as well as purges.
This is an add-on and requires access to the 60-akamai-connector repository.
This is an add-on.
It includes vmod_deviceatlas used
for device identification.
This is an add-on and requires access to the 60-deviceatlas repository.
This package is specific to RHEL and defines an SELinux policy for varnish-plus. More info on SELinux and Varnish is here.
This package contains development files for varnish-plus.
This is an add-on.
It includes the VCL and vmod used to integrate ModSecurity.
This is an add-on and requires access to the 60-waf repository.
The broadcaster is a
server that will dispatch HTTP requests to clusters of Varnish servers. It is an
integral part of VHA6
setups, but it is also used as a standalone tool to allow pre-warming and
purging at scale.
For auto-scaling clusters, please see varnish-discovery too.
This tool
is able to list server from various sources (DNS, k8s, AWS, etc.) and
write configuration files for other tools to use, such as the broadcaster.
VCS collects information for the Varnish logs to create time-series aggregated at the cluster level. It is composed of a central server collecting information from agents installed on each Varnish server.
This is the VCS agent.
The varnish-controller-agent contains the agent used to manage
the Varnish server in a Varnish Controller setup.
The varnish-controller-brainz contains the brainz which is used
to control a Varnish Controller setup.
The varnish-controller-api-gw contains the api-gw which is used
to access a Varnish Controller setup via REST API.
The varnish-controller-cli contains the vcli which is used
to manage a Varnish Controller setup via command line interface towards the Varnish Controller API-GW(s).
The varnish-controller-ui contains the ui which is used
to manage a Varnish Controller setup via a web interface. This package also includes the UI server which
the single page application talks to.
The varnish-controller-nats contains the nats-server which is used
as the message bus between all Varnish Controller components.
The varnish-controller-router contains the router which is used
to perform DNS and HTTP 302 redirect based traffic routing.