Varnish VCL for Drupal

Drupal 8 is still in development.

What specific settings are you looking to know about? The thing about Varnish is the default VCL works pretty well out of the box, and is always running in the background; you only need to handle those things that need special treatment.

I've made a number of tweaks to mine over the time I've been using it, each one based on changes I've discovered I need through watching it run. That's almost always the best bet for you too - just install it, watch it run, keep an eye on the hit-rate through something like Munin, and then work out how to solve any problems you run into.

All my tweaks have been nothing to do with Drupal - except one, and that wasn't in the VCL. (I increased connect_timeout to 600 in the daemon startup arguments - I discovered that Drupal sites needed a higher value.)

One more thing - have they tried some of the other things that can be done for content that is only updated daily? Are the caching values set high enough in the Admin > Performance screen? Have they considered using a CDN for their images / CSS files (with the CDN module) so that those static resources don't even hit Apache (or whatever httpd you are using)? Those things come first. For example, without getting the caching settings right on the site, Varnish won't cache much anyway because it reads and respects those headers.