)]}'
{
  "log": [
    {
      "commit": "05e482e3b905b1a32575239da6d6280ea4182efe",
      "tree": "cf2a72d6f2abd0195c1bd7c3bf33a9ab98a4eb98",
      "parents": [
        "80f9174752fd4ccb8d260c37936383b00f92d87d"
      ],
      "author": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Wed Nov 04 11:05:51 2026 +0100"
      },
      "committer": {
        "name": "Matthias Andreas Benkard",
        "email": "code@mail.matthias.benkard.de",
        "time": "Wed Nov 04 11:30:15 2026 +0100"
      },
      "message": "local-path-storage: Create ZFS datasets in the host mount namespace.\n\nThe setup hook ran `zfs create`/`zfs mount` inside the helper pod, so\nthe new dataset was mounted only in the helper container\u0027s mount\nnamespace.  Workloads wrote into the parent dataset rpool/var/k8s, and\nat the next host reboot the (empty) child dataset was mounted on top,\nhiding the data.  This is what wiped Garage\u0027s apparent state after the\nreboot on 2026-11-03.\n\nRun the helper pod with hostPID and perform all ZFS and filesystem\noperations via `nsenter -t 1 -m`, using the host\u0027s zfs binary.  Fail\nprovisioning if the dataset does not end up mounted on the host.\n\nlocal-path-storage.orig.yaml is a snapshot of the live resources before\nthis change.  Note that the provisioner (v0.0.19) reads helperPod.yaml\nonly at startup and must be restarted after changing it.\n\nCo-Authored-By: Claude Opus 5.5 \u003cnoreply@anthropic.com\u003e\nChange-Id: Id4e24bf1fca214a25ea207291cb10ff9500869e0\n"
    }
  ]
}