I recently moved to garden 0.13 and am trying to migrate old garden 0.12 configurations to 0.13 and have hit an error: ✖ providers → Failed processing resolve provider local-kubernetes (took 0.45 sec). This is what happened: Failed processing resolve provider local-kubernetes (took 0.45 sec). This is what happened: Error: Cannot parse content. No Content-Type defined. at ObjectSerializer.parse (file:///home/bryankwok/.local/share/garden/1704780732-ScZIxCW.r/rollup/garden.mjs:571760:21) at CoreV1ApiResponseProcessor.readNamespacedPodLogWithHttpInfo (file:///home/bryankwok/.local/share/garden/1704780732-ScZIxCW.r/rollup/garden.mjs:605869:111) at process.processTicksAndRejections (node:internal/process/task_queues:95:5) at async retry (file:///home/bryankwok/.local/share/garden/1704780732-ScZIxCW.r/rollup/garden.mjs:702394:20) at async requestWithRetry (file:///home/bryankwok/.local/share/garden/1704780732-ScZIxCW.r/rollup/garden.mjs:702420:20) at async file:///home/bryankwok/.local/share/garden/1704780732-ScZIxCW.r/rollup/garden.mjs:706237:19 at async Promise.all (index 0) at async file:///home/bryankwok/.local/share/garden/1704780732-ScZIxCW.r/rollup/garden.mjs:706300:25 at async Promise.all (index 0) at async getFormattedPodLogs (file:///home/bryankwok/.local/share/garden/1704780732-ScZIxCW.r/rollup/garden.mjs:706295:21) ──────────────────────────────────────────────────────────────────────────────────────────────────────── toKubernetesError encountered an unknown error unexpectedly during Kubernetes API: readNamespacedPodLog: toKubernetesError encountered an unknown error unexpectedly during readNamespacedPodLog: Cannot parse content. No Content-Type defined. Failed resolving one or more providers: - local-kubernetes Running this on WSL2 for a local kind cluster.

Hi @many-pizza-75746 and thank you so much for the bug report! I'll flag this with our engineers to take a look 👀