From 77f1bdc6b5d733071aceaaa3a4ae62a3ec42860e Mon Sep 17 00:00:00 2001 From: dfitzmau Date: Fri, 10 Nov 2023 12:20:02 +0000 Subject: [PATCH] OCPBUGS-10640: Added clarification point to disk partition BM doc --- modules/installation-user-infra-machines-advanced.adoc | 9 ++++----- 1 file changed, 4 insertions(+), 5 deletions(-) diff --git a/modules/installation-user-infra-machines-advanced.adoc b/modules/installation-user-infra-machines-advanced.adoc index cf1194a15b6e..5413c69edcee 100644 --- a/modules/installation-user-infra-machines-advanced.adoc +++ b/modules/installation-user-infra-machines-advanced.adoc @@ -87,11 +87,10 @@ officially supported for mounting `/var` or a subdirectory of `/var`, such as `/ ==== For disk sizes larger than 100GB, and especially disk sizes larger than 1TB, create a separate `/var` partition. See "Creating a separate `/var` partition" and this link:https://access.redhat.com/solutions/5587281[Red Hat Knowledgebase article] 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. -==== + +* Kubernetes supports monitoring of the following two types of file system partitions: +** `/var/lib/containers` in the same partition as `/var`. +** `/var/lib/containers` in a separate partition from `/var`. * Retaining 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.