Debugging Network Stalls on Kubernetes

Re:Debugging Network Stalls on Kubernetes by tra3 on Saturday November 23, 2019 @02:14PM (#21615868)

Can you recommend some alternatives to k8s that are cloud provider agnostic?

I have 3 docker compose nodes that I manage manually. I will shortly need another one.

Seems like time for an orchestrator. If I squint swarm is a reasonable solution but k8s hysteria is sweeping me along..

[ Parent | on HN ]

Re:Debugging Network Stalls on Kubernetes by pojzon on Sunday November 24, 2019 @05:20AM (#21619489)

There is no such a thing as "Cloud Agnostic". Be it K8S on AWS or Azure or GCP, each one has its own quirks that will make K8S run better or worse or even terrible.

Abstraction of some things on orchestration level does not mean there is no and will be no cloud specific code injected there. Actually there is a ton of this cloud specific code in there and when something stops working the way you want it to -> the solution often times is to write even more vendor locking code.

Instead of looking for "Cloud Agnostic" solution, find a solution that fits your use case the best. Using managed services if researched correctly can give many adventages. But like with everything that requires A LOT of knowledge about them and your domain.

[ Parent | on HN ]

Re:Debugging Network Stalls on Kubernetes by tra3 on Monday November 25, 2019 @01:29PM (#21631179)

It's interesting that you say that. Are you talkign about the hosted offerings then? If I spin up my own k8s "on metal" in GCP, would there still be something GCP specific to it?..

[ Parent | on HN ]