4 ms·
It’s not PR. It’s being accurate that this has nothing to do with Kubernetes.
by manigandham 7y ago
It’s not PR. It’s being accurate that this has nothing to do with Kubernetes.
- acdha 7y agoI would not describe a service which is only ever used on Kubernetes workers and is only necessary for code running on Kubernetes as having nothing to do with Kubernetes. The fact that you and the OP are so emotionally driven to find a way to dismiss it is what makes it sound like PR — why not just acknowledge there's a real problem which is being fixed and be glad someone documented it well enough to save other people time? Nobody is saying that Kubernetes is bad, or that you shouldn't use it, only that there's an interaction which Java users should know about if they're running on AWS.
- manigandham 7y agoYou're being strangely aggressive about this. Nobody cares about PR here, nor is anyone denying anything. We're just being accurate. KIAM and the Java SDK have bad timeout overlap. That's the problem, has nothing to do with Kubernetes, and looks like it's well documented and now resolved.
- acdha 7y agoThis was a well-written post about a problem a lot of people would encounter with a common Kubernetes deployment. Instead of talking about that, most of the comments were people complaining about the title.