You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: keps/sig-node/2400-node-swap/README.md
+2-5Lines changed: 2 additions & 5 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -228,9 +228,9 @@ The main concern would be swapping in the critical services on the control plane
228
228
229
229
##### Use of a dedicated disk for swap
230
230
231
-
We recommend using a separate disk for your swap partition. With [encryption](#security-risk), an encrypted disk is recommended for swap.
231
+
We recommend using a separate disk for your swap partition. We recommend the separate disk be [encrypted](#security-risk).
232
232
If swap is on a partition or the root filesystem, workloads can interfere with system processes needing to write to disk.
233
-
If they occupy the same disk, it's possible processes can overwhelm swap and throw off the I/O of kubelet/cri-o/systemd, which would affect other workloads
233
+
If they occupy the same disk, it's possible processes can overwhelm swap and throw off the I/O of kubelet/container runtime/systemd, which would affect other workloads
234
234
235
235
##### Swap as the default
236
236
@@ -332,9 +332,6 @@ clusters).
332
332
333
333
This user story is addressed by scenarios 1 and 2, and could benefit from 3.
334
334
335
-
It turns out that we discovered usecases where someone areas set `--fail-swap-on=false`
336
-
to allow for swap enabled nodes for local development.
0 commit comments