[7.6] cc74ad93a whats-new: Mention VSM_NOPID

[Dridi Boukelmoune]

commit cc74ad93a32627e8b24aa2348871fd89630d410d
Author: Dridi Boukelmoune <dridi.boukelmoune at gmail.com>
Date:   Tue Sep 17 08:35:11 2024 +0200

    whats-new: Mention VSM_NOPID
    
    Spotted by @gquintard who tripped on the PID 1 check that has already
    proven its worth.

diff --git a/doc/sphinx/whats-new/changes-7.6.rst b/doc/sphinx/whats-new/changes-7.6.rst
index e3085e8bd..885b911f8 100644
--- a/doc/sphinx/whats-new/changes-7.6.rst
+++ b/doc/sphinx/whats-new/changes-7.6.rst
@@ -20,6 +20,12 @@ The environment variable ``VARNISH_DEFAULT_N`` now provides the default "varnish
 name" / "workdir" as otherwise specified by he ``-n`` argument to ``varnishd``
 and ``varnish*`` utilities except ``varnishtest``.
 
+Programs attaching to ``varnishd``'s shared memory are now performing more
+precise status checks of the ``varnishd`` process. They should in particular
+better detect restarts of the process. This comes with signal-based liveness
+checks that can be disabled when ``VSM_NOPID`` is exported to the environment
+of utilities like ``varnishlog``, ``varnishstat`` or ``varnishncsa``.
+
 varnishd
 ========
 
diff --git a/doc/sphinx/whats-new/upgrading-7.6.rst b/doc/sphinx/whats-new/upgrading-7.6.rst
index 4f30f4c02..61378e5c1 100644
--- a/doc/sphinx/whats-new/upgrading-7.6.rst
+++ b/doc/sphinx/whats-new/upgrading-7.6.rst
@@ -9,6 +9,14 @@ besides the actual upgrade.
 
 The changes mentioned below are considered noteworthy nevertheless:
 
+Noteworthy changes for container workloads
+==========================================
+
+When ``varnishd`` runs in a different PID namespace on Linux, typically in a
+container deployment, ``VSM_NOPID`` must be added to the environment of other
+containers attaching themselves to ``varnishd``'s environment variable. This
+will otherwise fail liveness checks performed by VSM consumers.
+
 Noteworthy changes when upgrading varnishd
 ==========================================