)]}'
{
  "commit": "6888873fad889bfb7cd594b4208798f80eb60f43",
  "tree": "860ca3a83e6a6667888ec8595cc332f44e1cb6aa",
  "parents": [
    "29ac140c4cbdb8dd8d71863de8c9b4473a1c0215"
  ],
  "author": {
    "name": "Tim Windelschmidt",
    "email": "tim@monogon.tech",
    "time": "Thu Aug 03 14:25:28 2023 +0000"
  },
  "committer": {
    "name": "Tim Windelschmidt",
    "email": "tim@monogon.tech",
    "time": "Tue Aug 29 10:08:29 2023 +0000"
  },
  "message": "metropolis/node: dont allocate node ports in constructor\n\nAll good things are three, and this should be the final installment in\nthe saga of getting ports reserved. The Kubernetes codebase always\nstarts a recovery after initialization of a new port allocator, which\ncurrently makes it very unhappy as we already allocated the system\nports, but we are trying to do the same in the recovery by pretending to\nbe a service. Anyway, this removes the initial part of the patch and\nonly uses the recovery way of reserving the ports. This still creates an\nannoying message sometimes, but I can\u0027t find the code path which creates\nthem.\n\nChange-Id: Ib7d9ec5d00cbde7371d876c31c63b5312024a187\nReviewed-on: https://review.monogon.dev/c/monogon/+/2027\nReviewed-by: Lorenz Brun \u003clorenz@monogon.tech\u003e\nTested-by: Jenkins CI\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "ac201a8e653b53c7f39699a2ba15ae51c13f1c6d",
      "old_mode": 33188,
      "old_path": "third_party/go/patches/k8s-reserve-metropolis-ports.patch",
      "new_id": "1756d7b6398c956ff8d1dd340c4c6ff262ea34e6",
      "new_mode": 33188,
      "new_path": "third_party/go/patches/k8s-reserve-metropolis-ports.patch"
    }
  ]
}