[crb]

I collaborate with the team at Google who work on Kubernetes, and I know that other platforms are given a lot of love - we test end-to-end on AWS, for example.

If you're interested in getting involved in Kubernetes-on-something-else, we'd love to hear from you. Drop by Slack at slack.k8s.io!

[KirinDave]

So is the AWS binding not full of landmines now? With misleading defaults, a bad logging configuration that will assuredly fall over if it hits serious load, and a way to diagnose failures on the minions without resorting to AWS sorcery?

Can I run more than 1 cluster per account AZ without a silent but very nasty failure condition where both clusters become wedged?

I have stuff in production on it and I need to take it down because the entire cluster is unreliable. Mostly because there are frustrating bugs in disk space management that hurt clusters.

I really like Kubernetes and you can see I've carried water for it here. I've been trying to tie it to mbrace because thatz be a nice cloud portability. But I'm much more impressed with the GCE experience than the AWS experience.

[crb]

I honestly don't know, but I do know that the GitHub issue tracker is the system of record for all these things, and if you report them there, they will be fixed very quickly. These sound like things we'd want to know about and I'm not close enough to the AWS experience to know if it's as bad as you say!