Guido Maria Serra+Fenaroli

uhmm... ur patch doesn't seem to solve my problem ``` (jsonrpc)dyn-86-client:scripts zeph$ pip install ../../dejw-jsonrpclib Unpacking /Users/zeph/tmp/dejw-jsonrpclib Running setup.py egg_info for package from file:///Users/zeph/tmp/dejw-jsonrpclib Installing collected packages: jsonrpclib Running setup.py...

k, u are not overriding... feel free to pull my change https://github.com/txtr/jsonrpclib/commit/4e4938fb2ca2517a822d330d211f90d5ec2662db if of any help

I'd really appreciate to see this feature from "dejw" in the main source stream ;)

in particular.. I can't use the Confluence JSON-RPC calls cause the library is sending out the wrong headers... - https://developer.atlassian.com/display/CONFDEV/Confluence+JSON-RPC+APIs "jsonrpclib.jsonrpc.ProtocolError: (-32600, u'JSON-RPC requests must have the Content-type: application/json')"

@xiehan I'd really love to be more constructive on detailing what's wrong with the upgrade procedure... but it is the 3rd time in 2years that I pick up a `cdktf`...

not really... there are just one from a [russian provider](https://github.com/yandex-cloud/k8s-csi-s3) and one from aws (specific to their EKS)

leaving on a single container, the system wont' stand a reboot, similar to https://github.com/kubernetes-sigs/kind/issues/2879#issuecomment-2472643645 erroring on kube-api calls with `net/http: TLS handshake timeout`

it now works (after moving GPUs to a separate container)... but still, struggles with the performance (it's a 192GB RAM machine, not the Hetzner mentioned above)  here's the status...

logs are full of ` Normal SandboxChanged 25m (x2 over 27m) kubelet Pod sandbox changed, it will be killed and re-created.` on the failing containers

suspecting this might be related https://github.com/canonical/microk8s/issues/2790#issuecomment-1421101259