From 9fbda97d919fa95f15aae8724ef3f4e2e4f365e6 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 | 7 ++----- 1 file changed, 2 insertions(+), 5 deletions(-) diff --git a/modules/installation-user-infra-machines-advanced.adoc b/modules/installation-user-infra-machines-advanced.adoc index cf1194a15b6e..d6f90cc0cf73 100644 --- a/modules/installation-user-infra-machines-advanced.adoc +++ b/modules/installation-user-infra-machines-advanced.adoc @@ -87,11 +87,8 @@ 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 only two file system partitions: a single filesystem for `/var` or a dedicated filesystem for your container runtime. One could use a separate partition for `/var/lib/containers`. These are the only two supported ways to have Kubernetes monitor the filesystem. * 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.