I went through the whole storage section and also read few articles about it on the web to get a better picture. However, I’m still wondering whether K8S storage is actually ever used in the real world?
Most of the needs for storage is database. This could be covered by cloud provider though (RDS or Elasticsearch in AWS). Providing an external one to the k8s seems also like way less hassle.
Static content? Only in a case when your company has a lot of other micro services so the hassle with setting up the k8s pays off. For a simple web page though that’s not really good fit. Not even mentioning services like S3 on AWS.
Could you describe use-cases where k8s storage is really used in prod and there is no better alternative?
1 Answers
There will always be the case :).
For example your app requires a specific database engine that is not available as PaaS with your cloud provider, or they have that engine but only non-optimal versions for your app. In this case a containerized DBMS tailored to your need is the only option.
Another example, your app requires a very tight compliance stuff and one of them is not to use the Internet as communication channel to database (or similar so). Not every DB-as-a-Service of every cloud provider has the ability to communicate through VPC connection. So again a containerized DBMS is the only option if your cloud provider cannot provide private network connection to their DB-as-a-Service.
I was also confused the focus on that topic. I can’t really think of a Use Case when I would want to do this. None the less it’s good to know.