fix: integrate inotify parameter setup into environmentSetup deploy flow

src/environmentSetup/environmentSetup.sh

@@ -348,7 +348,8 @@ env_setup_local_cluster() {
         check_resources_ok
         ensure_python_venv
         add_hosts
-
+        increase_inotify_params
+
         if ! is_local_cluster_installed; then
             install_k3s
             $UTILS_DIR/install-k9s.sh > /dev/null 2>&1

src/environmentSetup/k8s.sh

@@ -293,6 +293,34 @@ install_k8s_tools() {
 }
 
 
+#------------------------------------------------------------------------------
+# Function: increase_inotify_params
+# Description: Increases inotify limits required for Kubernetes/container
+#              workloads. Without this, vnext pods hit EMFILE errors on startup.
+#------------------------------------------------------------------------------
+increase_inotify_params() {
+    log_step "Increase inotify limits for Kubernetes workloads"
+    local SYSCTL_FILE="/etc/sysctl.d/99-inotify.conf"
+
+    sysctl -w fs.inotify.max_user_watches=1048576 >/dev/null 2>&1 || {
+        log_warn "Failed to set fs.inotify.max_user_watches"
+        return 1
+    }
+    sysctl -w fs.inotify.max_user_instances=1024 >/dev/null 2>&1 || {
+        log_warn "Failed to set fs.inotify.max_user_instances"
+        return 1
+    }
+
+    cat <<EOF > "${SYSCTL_FILE}"
+# Increased inotify limits for Kubernetes/container workloads
+fs.inotify.max_user_watches = 1048576
+fs.inotify.max_user_instances = 1024
+EOF
+
+    sysctl --system >/dev/null 2>&1
+    log_ok
+}
+
 #------------------------------------------------------------------------------
 # Function : report_cluster_info
 # Description: Reports basic information about the Kubernetes cluster.