Varnish Controller 7.0.0 Release

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 documentation has been divided into its own section for Version 7. This is to make it easier and to avoid no longer supported commands and examples.

• Support for Long Lived Tokens, see Sessions.
• Support for file versioning, see files.
• Support for Git managed deployments, see Git.
• New deployment procedure, see VCLGroups.
  • Deployments has been removed and replaced with TagSets directly on VCLGroups.
  • VCLGroups are no longer connected via files, they are deployed individually.
  • Deploying files can be verified on a given set of matching agents, all matching agents or a random matching agent.
  • Deploy logs for rollback of previously deployed files
  • Keep on failure always on.
  • Deploy VCLGroup from git repository
• Support for ACME (Let’s Encrypt), see ACME.
  • Creation of accounts and certificates
  • Automatic renewal of certificates
• New database layer for performance improvements and stability.
• Brainz now requires git as a dependency when installing the brainz package.
• The default minimum TLS version for new certificates created in the controller has been changed from TLSv1.3 to TLSv1.2.
• Certificates now have an allSans option to load all SAN entries into Varnish, including wildcards.
• Support to append a single domain ID to a VCLGroup.
• Dropping support for a couple of old distributions that has reached End Of Life:
  • Ubuntu Xenial
  • Ubuntu Bionic
  • Ubuntu Focal
  • Debian Stretch
  • Debian Buster
  • Centos 7
• This release requires Varnish Enterprise 6.0.8r2 or later.
• All components has been built with latest Go 1.24.
• Nats-server version 2.11.0

See Varnish Controller Changelog for more details on the changes and the upgrade notes for more details on how to upgrade.