)]}'
{
  "commit": "1dd0c6591533bf63389e81a2104bca3c8326e871",
  "tree": "e33a710087b67dfe7f34e8434cff8885dc38420c",
  "parents": [
    "456961d6589c1afec75954ca94ed631e1f380566"
  ],
  "author": {
    "name": "Lorenz Brun",
    "email": "lorenz@monogon.tech",
    "time": "Tue Feb 20 18:45:06 2024 +0100"
  },
  "committer": {
    "name": "Lorenz Brun",
    "email": "lorenz@monogon.tech",
    "time": "Tue Feb 20 18:12:12 2024 +0000"
  },
  "message": "m/n/kubernetes: improve CSI registration reliability\n\nKubelet\u0027s plugin registration mechanism is quite awful, it\nrelies on being notified by inotify that a new registration socket has\nbeen placed into a specific path, which it then interrogates and\nreports back if the registration succeeded.\n\nThat registration sometimes involves network operations which are prone\nto failure. It reports that failure back to the registration server\nasynchronously but does not attempt to retry the process.\n\nTo actually get Kubelet to retry, one needs to remove and recreate the\nregistration socket.\n\nThis change implements such a mechanism, recreating the socket and\nregistration server on every reported registration failure.\n\nSupervisor backoff is used to prevent busy-looping on non-transient\nerrors.\n\nChange-Id: I79eaf0efdf55ccdede15d8cee42cda7c276e4b50\nReviewed-on: https://review.monogon.dev/c/monogon/+/2785\nReviewed-by: Serge Bazanski \u003cserge@monogon.tech\u003e\nReviewed-by: Tim Windelschmidt \u003ctim@monogon.tech\u003e\nTested-by: Jenkins CI\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ab9549d68c89965e010fa7a6a5652c04b8355969",
      "old_mode": 33188,
      "old_path": "metropolis/node/kubernetes/csi.go",
      "new_id": "58c381a402ce753d94d8864048d78f0385050ad5",
      "new_mode": 33188,
      "new_path": "metropolis/node/kubernetes/csi.go"
    }
  ]
}