Docker卷与Kubernetes数据库持久卷 [英] Docker volume vs Kubernetes persistent volume for databases

问题描述

两个Docker映像和Kubernetes集群具有在主机，单独的容器或仅某种形式的云/网络存储机制上配置持久性存储的机制.

Both Docker images & Kubernetes clusters have mechanisms to configure persistent storage on the host machine, a separate container, or just some form of cloud/network storage mechanism.

我试图了解它们在用例中的不同之处，以及为什么要在另一种情况下使用它们.对于上下文，我还要考虑事务数据库的持久性，而不是日志文件或共享文件/文件夹访问.

I'm trying to understand how they are different in use cases and why you'd use one over the other. For context, I'm also looking at this more with transactional database persistence in mind, rather than log files or for a shared file/folder access.

提前谢谢！

推荐答案

在Kubernetes之类的群集上使用docker卷无法提供数据持久性.工作负载可以安排在其他节点上，您就可以完成工作.要在K8S群集中提供持久存储，您需要使用K8S解决方案来解决该问题.

using docker volumes on a cluster like Kubernetes gives you no data persistency. The workload can get scheduled on different node and you're done. To provide persistent storage in K8S cluster you need to use K8S solution to the problem.

这篇关于Docker卷与Kubernetes数据库持久卷的文章就介绍到这了，希望我们推荐的答案对大家有所帮助，也希望大家多多支持IT屋！