Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

link to graph driver details is broken #791

Open
wants to merge 1 commit into
base: stable/v19.01
Choose a base branch
from
Open

link to graph driver details is broken #791

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/dag/kubernetes/storage_kubernetes_infrastructure_services.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -8,7 +8,7 @@ Trident focuses on providing persistence to Kubernetes applications, but before

**Node-local container storage, a.k.a. graph driver storage**

One of the often overlooked components of a Kubernetes deployment is the storage which the container instances consume on the Kubernetes cluster nodes, usually referred to as `graph driver storage <https://success.docker.com/article/an-introduction-to-storage-solutions-for-docker-caas#graphdriverstorage>`_. When a container is instantiated on a node it consumes capacity and IOPS to do many of it's operations as only data which is read from or written to a persistent volume is offloaded to the external storage. If the Kubernetes nodes are expected to host dozens, hundreds, or more containers this may be a significant amount of temporary capacity and IOPS which are expected of the node-local storage.
One of the often overlooked components of a Kubernetes deployment is the storage which the container instances consume on the Kubernetes cluster nodes, usually referred to This link is broken - please correct Thanks! > as `graph driver storage <https://success.docker.com/article/an-introduction-to-storage-solutions-for-docker-caas#graphdriverstorage>`_. When a container is instantiated on a node it consumes capacity and IOPS to do many of it's operations as only data which is read from or written to a persistent volume is offloaded to the external storage. If the Kubernetes nodes are expected to host dozens, hundreds, or more containers this may be a significant amount of temporary capacity and IOPS which are expected of the node-local storage.

Even if you don't have a requirement to keep the data, the containers still need enough performance and capacity to execute their application. The Kubernetes administrator and storage administrator should work closely together to determine the requirements for graph storage and ensure adequate performance and capacity is available.

Expand Down