From 58bbdad7f7e9e52476ba83132be53af2f6192824 Mon Sep 17 00:00:00 2001
From: Austin Macdonald <austin@dartmouth.edu>
Date: Tue, 6 Aug 2024 17:20:46 -0500
Subject: [PATCH 1/3] Document inotify config for kind deployments

Fixes #495
---
 docs/docs/how-tos/nebari-local.md | 9 +++++++++
 1 file changed, 9 insertions(+)

diff --git a/docs/docs/how-tos/nebari-local.md b/docs/docs/how-tos/nebari-local.md
index 15335b4a9..46543279d 100644
--- a/docs/docs/how-tos/nebari-local.md
+++ b/docs/docs/how-tos/nebari-local.md
@@ -159,6 +159,15 @@ security:
         tag: sha-b4a2d1e
 ```
 
+### Increase fs watches
+
+Depending on your host system, you may need to increase the `fs.inotify.max_user_watches` and
+`fs.inotify.max_user_instances kernel parameters` if you see a `too many open files` in the logs of
+a failing pod.
+
+See the [kind troubleshooting
+docs](https://kind.sigs.k8s.io/docs/user/known-issues/#pod-errors-due-to-too-many-open-files)
+
 ## Deploying Nebari
 
 With the `nebari-config.yaml` configuration file now created, Nebari can be deployed for the first time with:

From 8a2cdd862781bc3b3d23f0fb5607323178dadce7 Mon Sep 17 00:00:00 2001
From: Austin Macdonald <austin@dartmouth.edu>
Date: Thu, 26 Sep 2024 11:12:14 -0500
Subject: [PATCH 2/3] Add user watches and instances snippet

---
 docs/docs/how-tos/nebari-local.md | 5 +++++
 1 file changed, 5 insertions(+)

diff --git a/docs/docs/how-tos/nebari-local.md b/docs/docs/how-tos/nebari-local.md
index 46543279d..bba889afd 100644
--- a/docs/docs/how-tos/nebari-local.md
+++ b/docs/docs/how-tos/nebari-local.md
@@ -165,6 +165,11 @@ Depending on your host system, you may need to increase the `fs.inotify.max_user
 `fs.inotify.max_user_instances kernel parameters` if you see a `too many open files` in the logs of
 a failing pod.
 
+```bash
+sudo sysctl fs.inotify.max_user_watches=524288
+sudo sysctl fs.inotify.max_user_instances=512
+```
+
 See the [kind troubleshooting
 docs](https://kind.sigs.k8s.io/docs/user/known-issues/#pod-errors-due-to-too-many-open-files)
 

From 1b0ae94b73e4fc307b90cd008be30ea9d7c03e15 Mon Sep 17 00:00:00 2001
From: Austin Macdonald <austin@dartmouth.edu>
Date: Thu, 26 Sep 2024 11:13:16 -0500
Subject: [PATCH 3/3] Apply suggestions from code review

Co-authored-by: Kim Pevey <kcpevey@quansight.com>
---
 docs/docs/how-tos/nebari-local.md | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)

diff --git a/docs/docs/how-tos/nebari-local.md b/docs/docs/how-tos/nebari-local.md
index bba889afd..30b98a8c9 100644
--- a/docs/docs/how-tos/nebari-local.md
+++ b/docs/docs/how-tos/nebari-local.md
@@ -162,7 +162,7 @@ security:
 ### Increase fs watches
 
 Depending on your host system, you may need to increase the `fs.inotify.max_user_watches` and
-`fs.inotify.max_user_instances kernel parameters` if you see a `too many open files` in the logs of
+`fs.inotify.max_user_instances kernel parameters` if you see the error "too many open files" in the logs of
 a failing pod.
 
 ```bash
@@ -171,7 +171,7 @@ sudo sysctl fs.inotify.max_user_instances=512
 ```
 
 See the [kind troubleshooting
-docs](https://kind.sigs.k8s.io/docs/user/known-issues/#pod-errors-due-to-too-many-open-files)
+docs](https://kind.sigs.k8s.io/docs/user/known-issues/#pod-errors-due-to-too-many-open-files) for more information.
 
 ## Deploying Nebari