Read on Twitter
Interesting observation: I've never seen anyone who can say that he is an expert in Kubernetes.
Some people were experienced in one area or another, but not the whole flow with all the nuances, which is required for debugging non-trivial issues (which are very common).
Some people were experienced in one area or another, but not the whole flow with all the nuances, which is required for debugging non-trivial issues (which are very common).
As part of work at Tyk I doing quite a lot of customer support with big companies.
The situation with Kubernetes there is even worse. No one has internal experts, everything is offloaded to consultancies, and they have no true experts as well.
The situation with Kubernetes there is even worse. No one has internal experts, everything is offloaded to consultancies, and they have no true experts as well.
Itsio and service mesh complicates things even more, by introducing more abstractions and moving parts.
Hosted solutions like GKE or EKS help a bit, but only simplify installation and maintenance. No one will stop you from shooting yourself in the foot (and you will).
Hosted solutions like GKE or EKS help a bit, but only simplify installation and maintenance. No one will stop you from shooting yourself in the foot (and you will).
It is a common misconception about the software in general: if someone smart developed the software, it will work as promised.
if your business depends on some complex system, and you do not have a direct support channel with the people who build it: you are in trouble.
if your business depends on some complex system, and you do not have a direct support channel with the people who build it: you are in trouble.
So far the only acceptable experience I had with containerized environments is very DX focused @HashiCorp Nomad https://www.nomadproject.io/ with a simple promise and a small number of moving parts, which actually can fit to the head of a single person.
We need more abstractions, which are built on simple understandable building blocks, and a user flows driven by DX and UX specialists.
I would rather have multiple tools that do one thing right, then the one which can do everything.
I would rather have multiple tools that do one thing right, then the one which can do everything.
