mirror of
https://github.com/openshift/openshift-docs.git
synced 2026-02-05 21:46:22 +01:00
OSDOCS-3640: add note for large disks
This commit is contained in:
committed by
openshift-cherrypick-robot
parent
8a921eef84
commit
53c5cd14cb
@@ -24,7 +24,12 @@ officially supported for making `/var` or a subdirectory of `/var`, such as `/va
|
||||
+
|
||||
[IMPORTANT]
|
||||
====
|
||||
Kubernetes supports only two filesystem partitions. If you add more than one partition to the original configuration, Kubernetes cannot monitor all of them.
|
||||
For disk sizes larger than 100GB, and especially disk sizes larger than 1TB, create a separate `/var` partition. See "Creating a separate `/var` partition" for more information.
|
||||
====
|
||||
+
|
||||
[IMPORTANT]
|
||||
====
|
||||
Kubernetes supports only two file system partitions. If you add more than one partition to the original configuration, Kubernetes cannot monitor all of them.
|
||||
====
|
||||
* Retain existing partitions: For a brownfield installation where you are reinstalling {product-title} on an existing node and want to retain data partitions installed from your previous operating system, there are both boot arguments and options to `coreos-installer` that allow you to retain existing data partitions.
|
||||
|
||||
@@ -41,6 +46,11 @@ For example:
|
||||
as more images and containers are added to a system.
|
||||
* `/var/lib/etcd`: Holds data that you might want to keep separate for purposes such as performance optimization of etcd storage.
|
||||
* `/var`: Holds data that you might want to keep separate for purposes such as auditing.
|
||||
+
|
||||
[IMPORTANT]
|
||||
====
|
||||
For disk sizes larger than 100GB, and especially larger than 1TB, create a separate `/var` partition.
|
||||
====
|
||||
|
||||
Storing the contents of a `/var` directory separately makes it easier to grow storage for those areas as needed and reinstall {product-title} at a later date and keep that data intact. With this method, you will not have to pull all your containers again, nor will you have to copy massive log files when you update systems.
|
||||
|
||||
|
||||
@@ -79,6 +79,11 @@ officially supported for mounting `/var` or a subdirectory of `/var`, such as `/
|
||||
+
|
||||
[IMPORTANT]
|
||||
====
|
||||
For disk sizes larger than 100GB, and especially disk sizes larger than 1TB, create a separate `/var` partition. See "Creating a separate `/var` partition" for more information.
|
||||
====
|
||||
+
|
||||
[IMPORTANT]
|
||||
====
|
||||
Kubernetes supports only two file system partitions. If you add more than one partition to the original configuration, Kubernetes cannot monitor all of them.
|
||||
====
|
||||
|
||||
@@ -101,6 +106,11 @@ For example:
|
||||
as more images and containers are added to a system.
|
||||
* `/var/lib/etcd`: Holds data that you might want to keep separate for purposes such as performance optimization of etcd storage.
|
||||
* `/var`: Holds data that you might want to keep separate for purposes such as auditing.
|
||||
+
|
||||
[IMPORTANT]
|
||||
====
|
||||
For disk sizes larger than 100GB, and especially larger than 1TB, create a separate `/var` partition.
|
||||
====
|
||||
|
||||
Storing the contents of a `/var` directory separately makes it easier to grow storage for those areas as needed and reinstall {product-title} at a later date and keep that data intact. With this method, you will not have to pull all your containers again, nor will you have to copy massive log files when you update systems.
|
||||
|
||||
|
||||
Reference in New Issue
Block a user