Quentin Machu

@dcowden > I'm still investigating the use of kubelet --resolve-conf, but what I'm really worried about is that all this is just a bandaid.. I have tried the other day,...

@brb Thanks! I haven't realized yesterday that the patched iptables was already in an Alpine release. My issue is surely still present and both `insert_failed` and `drop` are still increasing....

@dcowden You need to make sure you are calling iptables 1.6.2, otherwise you will not see the flag. One solution is to run iptables from within the weave container. As...

Just leaving a note here.. Because most Kubernetes deployments have kube-system services that require root privileges on the host (e.g. overlay networks), we will need to support `--userns=host`, and extend...

I am not entirely sure of the exact situation that re-creates that issue. It might be / have been an issue on AWS's side. I have spawned and attached ~500...

This basically happens *all the time* on my Kubernetes nodes, and completely screw over my Kubernetes clusters on C5s as, while EC2 thinks the volume is properly attached: EC2 will...

The volume never gets mounted, as shown in the `nvme list` above. The kernel fails to bring up the NVMe Controller for the device. Kubernetes is not the culprit, it...

After a few back and forth with AWS: > The behaviour you have observed with relation to Force Detach is expected, as this results in the EBS volume being removed...

Could we please re-open this issue for the time being, as multiple users are affected, and as it is being investigated as a real issue?

Does anyone know if this is still an issue on 1800.3.0 or 1828.0.0? It is preventing any Container Linux users from using m5/c5 machines reliability.