SearchThere is no magic here. Customers need to export current configurations and apply to a new running instance by themselves. It would take a bit of work but we really recommended to do. if customers do not want to lose any caching data or configurations. (You will lose all in-memory caching data anyhow.)
This guideline could be used as a backup guideline for interested customers.
Good news is, recently, we have implemented a robust solution for upgrading the products by simply running YUM or APT package managers. This solution is only for Varnish Custom Statistics (VCS) and Varnish Enterprise customers. Varnish Cache customers still need to export configurations by themselves.
Varnish Custom Statistics (VCS), Varnish Enterprise and Varnish Enterprise customers, we encouraged you to register for support and software update at: [https://info.varnish-software.com/varnish-plus-cloud-support]
Once you are registered and a welcome email does not contain upgrade instructions, please contact Varnish Software The Cloud Team to obtain a Master token and instructions how to setup a software repository.
/etc/varnish/varnish.paramsall *.vcl files/etc/default/varnishlog/etc/default/varnishncsa/etc/default/varnishall *.vcl files/etc/varnish/varnish.paramsall *.vcl filesMSE file backends/etc/default/varnishlog/etc/default/varnishncsa/etc/default/varnishall *.vcl filesMSE file backends/etc/varnish/vstatdprobe.params/etc/default/vstatdprobe/etc/varnish/vha-agent.params/etc/vha-agent/nodes.conf/etc/default/vha-agent/etc/vha-agent/nodes.conf/etc/hitch/hitch.params/etc/hitch/hitch.confSSL x509 certificate file/etc/default/hitch/etc/hitch/hitch.confSSL x509 certificate file/etc/varnish/vstatd.params/etc/default/vstatd