Nathan Grennan

I worked around the chicken and the egg problem by starting kubelet-rubber-stamp outside a container. I copied the binary out, and ran the commands below. I had to create a...

The actual kubelet error is below: ``` Mar 11 01:10:55 kube-frodo-master-01 kubelet[21378]: E0311 01:10:55.312832 21378 kuberuntime_gc.go:153] Failed to stop sandbox "6cfbb9f819b87cea54bfc00a52d1d04ea859b4ddf6e126ad7a68d098228b4068" before removing: rpc error: code = Unknown desc =...

Looks like kube-router is having trouble, but still kubelet insists that the cni should be up before starting a container. Error: ```cni.go:302] CNI failed to retrieve network namespace path: cannot...

I switched back to a dedicated kubelet certificate for the kubelets on the masters. This allows kube-router and kube-rubber-stamp to run normally. While still allowing the use of TLS bootstrapping...

A correction, it is mentioned in the package.json, but no license file or mention in the README.md. In addition full compliance with the license requires more than just a copy...

I am seeing what seems to be fake corruption on Fedora 40 with transmission-4.0.6-1.fc40. I have downgraded to transmission-4.0.2-1.fc36.x86_64 to see if it goes away.

@GodTamIt It is hard to prove a negative, but it seems to work without corruption.

My first corruption issue was with 4.0.6 on Fedora 40. I tried previous versions till I got to 4.0.2, and it works without corruption.

My issue seems to have disappeared. I stepped from 4.0.2 to 4.0.3 to 4.0.4 to 4.0.6 on Fedora 40. I have been on 4.0.6 for days with a higher than...

It again took days, but also saw the corruption bug with 4.0.3. I am currently testing 4.0.2 again.