Skip to content

Commit ee9fdf2

Browse files
authored
Merge pull request #32960 from EricPonvelle/Flagging-ContainerStorage
BZ1936731: Adds information on setting the mount options for container storage
2 parents 0eedac7 + 897ae24 commit ee9fdf2

File tree

2 files changed

+90
-11
lines changed

2 files changed

+90
-11
lines changed

modules/installation-disk-partitioning-upi-templates.adoc

Lines changed: 45 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -35,6 +35,51 @@ Because `/var` must be in place before a fresh installation of {op-system-first}
3535
If you follow the steps to create a separate `/var` partition in this procedure, it is not necessary to create the Kubernetes manifest and Ignition config files again as described later in this section.
3636
====
3737

38+
.Prerequisites
39+
40+
* If container storage is on the root partition, ensure that this root partition is mounted with the `pquota` option by including `rootflags=pquota` in the GRUB command line.
41+
42+
* If the container storage is on a partition that is mounted by `/etc/fstab`, ensure that the following mount option is included in the `/etc/fstab` file:
43+
+
44+
[source,terminal]
45+
----
46+
/dev/sdb1 /var xfs defaults,pquota 0 0
47+
----
48+
49+
* If the container storage is on a partition that is mounted by `systemd`, ensure that the `MachineConfig` object includes the following mount option as in this example:
50+
+
51+
[source,yaml]
52+
----
53+
spec:
54+
config:
55+
ignition:
56+
version: 3.1.0
57+
storage:
58+
disks:
59+
- device: /dev/sdb
60+
partitions:
61+
- label: var
62+
sizeMiB: 240000
63+
startMiB: 0
64+
filesystems:
65+
- device: /dev/disk/by-partlabel/var
66+
format: xfs
67+
path: /var
68+
systemd:
69+
units:
70+
- contents: |
71+
[Unit]
72+
Before=local-fs.target
73+
[Mount]
74+
Where=/var
75+
What=/dev/disk/by-partlabel/var
76+
Options=defaults,pquota
77+
[Install]
78+
WantedBy=local-fs.target
79+
enabled: true
80+
name: var.mount
81+
----
82+
3883
.Procedure
3984

4085
. Create a directory to hold the {product-title} installation files:
@@ -100,12 +145,6 @@ spec:
100145
+
101146
<1> The storage device name of the disk that you want to partition.
102147
<2> When adding a data partition to the boot disk, a minimum value of 25000 MiB (Mebibytes) is recommended. The root file system is automatically resized to fill all available space up to the specified offset. If no value is specified, or if the specified value is smaller than the recommended minimum, the resulting root file system will be too small, and future reinstalls of {op-system} might overwrite the beginning of the data partition.
103-
+
104-
[NOTE]
105-
====
106-
When creating a separate `/var` partition, you cannot use different instance types for worker nodes, if the different instance types do not have the same device name.
107-
====
108-
109148

110149
. Run `openshift-install` again to create Ignition configs from a set of files in the `manifest` and `openshift` subdirectories:
111150
+

modules/installation-disk-partitioning.adoc

Lines changed: 45 additions & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -48,6 +48,51 @@ Because `/var` must be in place before a fresh installation of
4848
by creating a machine config that is inserted during the `openshift-install`
4949
preparation phases of an {product-title} installation.
5050

51+
.Prerequisites
52+
53+
* If container storage is on the root partition, ensure that this root partition is mounted with the `pquota` option by including `rootflags=pquota` in the GRUB command line.
54+
55+
* If the container storage is on a partition that is mounted by `/etc/fstab`, ensure that the following mount option is included in the `/etc/fstab` file:
56+
+
57+
[source,terminal]
58+
----
59+
/dev/sdb1 /var xfs defaults,pquota 0 0
60+
----
61+
62+
* If the container storage is on a partition that is mounted by `systemd`, ensure that the `MachineConfig` object includes the following mount option as in this example:
63+
+
64+
[source,yaml]
65+
----
66+
spec:
67+
config:
68+
ignition:
69+
version: 3.1.0
70+
storage:
71+
disks:
72+
- device: /dev/sdb
73+
partitions:
74+
- label: var
75+
sizeMiB: 240000
76+
startMiB: 0
77+
filesystems:
78+
- device: /dev/disk/by-partlabel/var
79+
format: xfs
80+
path: /var
81+
systemd:
82+
units:
83+
- contents: |
84+
[Unit]
85+
Before=local-fs.target
86+
[Mount]
87+
Where=/var
88+
What=/dev/disk/by-partlabel/var
89+
Options=defaults,pquota
90+
[Install]
91+
WantedBy=local-fs.target
92+
enabled: true
93+
name: var.mount
94+
----
95+
5196
.Procedure
5297

5398
. Create a directory to hold the {product-title} installation files:
@@ -116,11 +161,6 @@ spec:
116161
+
117162
<1> The storage device name of the disk that you want to partition.
118163
<2> When adding a data partition to the boot disk, a minimum value of 25000 mebibytes is recommended. The root file system is automatically resized to fill all available space up to the specified offset. If no value is specified, or if the specified value is smaller than the recommended minimum, the resulting root file system will be too small, and future reinstalls of {op-system} might overwrite the beginning of the data partition.
119-
+
120-
[NOTE]
121-
====
122-
When creating a separate `/var` partition, you cannot use different instance types for worker nodes, if the different instance types do not have the same device name.
123-
====
124164

125165
. Run `openshift-install` again to create Ignition configs from a set of files in the `manifest` and `openshift` subdirectories:
126166
+

0 commit comments

Comments
 (0)