)]}'
{
  "commit": "79a1a8f9dd49afe8e0a2364c4586b8f39525b204",
  "tree": "2bf599ded06a18c5850cbf513e94fd0cf7ba3776",
  "parents": [
    "a8e23543e792505ea8a40bf544d857163696a25b"
  ],
  "author": {
    "name": "Lorenz Brun",
    "email": "lorenz@monogon.tech",
    "time": "Thu Mar 31 17:19:07 2022 +0200"
  },
  "committer": {
    "name": "Lorenz Brun",
    "email": "lorenz@monogon.tech",
    "time": "Mon Apr 04 19:45:00 2022 +0000"
  },
  "message": "m/n/k/authproxy: make use of SPDY through proxy work\n\nKubernetes still uses SPDY for interactive/streaming-type calls (like\nexec or port-forward). Our proxy uses a HTTP/2 backend connection to\nKubernetes\u0027s API server. A HTTP/2 stream cannot be upgraded to SPDY\nmeaning these API requests all fail. This implements a slightly ugly\nworkaround by using two HTTP transports, a regular transport which\nsupports HTTP/2 and a fallback transport which does not. The proxy\nselects the fallback transport if it detects that the request is trying\nto upgrade to SPDY.\n\nChange-Id: Idd44f58d07ec5570ddf8941ae7595225f47f254d\nReviewed-on: https://review.monogon.dev/c/monogon/+/645\nReviewed-by: Sergiusz Bazanski \u003cserge@monogon.tech\u003e\n",
  "tree_diff": [
    {
      "type": "modify",
      "old_id": "0477b88858aea634f5bbc1c37641ce98d7909ca6",
      "old_mode": 33188,
      "old_path": "metropolis/node/kubernetes/authproxy/authproxy.go",
      "new_id": "957cb8ac1a18abe2c61cd1a6634a4e3c834a6716",
      "new_mode": 33188,
      "new_path": "metropolis/node/kubernetes/authproxy/authproxy.go"
    }
  ]
}