4 ms·
> it's pure bliss in terms of reliability narrator: it is not. you're not trying very hard if you haven't hit a case where k8s will lead to you banging your he
by x86x87 4y ago
> it's pure bliss in terms of reliability
narrator: it is not. you're not trying very hard if you haven't hit a case where k8s will lead to you banging your heads on any available walls trying to understand a behavior in an edge case (here is one that made walls hate me: https://github.com/kubernetes/kubernetes/issues/96858 https://github.com/kubernetes/kubernetes/issues/96858 and I know of a half dozen developers that learned about this the hard way).
- hanikesn 4y agoLooks to me like an example of aws not having good defaults put of the box and not an k8s specific issue. Having to specific a `sleep 30` shutdown hook on pods is quite annoying though and some built-in should be added instead.
- shaklee3 4y agoexactly. if you read the bug it's clearly not a k8s issue. they cannot control aws jabbering elb bugs.
- x86x87 4y agoYou're missing the point. There is no cloud agnosticism and you need to understand the underlying cloud primitives although allegedly k8s isolates you from this.
- shaklee3 4y agoI'm not missing the point. The OP was specifically talking about a k8s bug that wasn't a k8s bug at all. You don't blame Linux for a poorly written application. If the cloud providers choose to add a bunch of uncommon options that has no counterpart in k8s that's their choice. but it doesn't mean k8s is a magic bullet that makes it so you don't have to do the bare minimum to understand the cloud providers.