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: pages/public_cloud/containers_orchestration/managed_kubernetes/configuring-sysctl-parameters-on-nodes-on-an-ovh-managed-kubernetes-cluster/guide.fr-fr.md
+10Lines changed: 10 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -59,6 +59,16 @@ And define the value of the sysctl key ```fs.inotify.max_user_watches``` based o
59
59
60
60
The DaemonSet will set the sysctl parameter "fs.inotify.max_user_watches" with the value you provided in the DaemonSet configuration on all nodes deployed into your Kubernetes Cluster.
61
61
62
+
> [!primary]
63
+
>
64
+
> Multiple sysctl parameters can be modified and adapted for your use cases. You can list them by running this command :
65
+
>
66
+
> ```bash
67
+
> $ kubectl run busybox --image=busybox:latest --rm=true -it --privileged=true -- sysctl -a
68
+
> ```
69
+
>
70
+
> This command will create a privileged busybox pod, will print all "sysctl" variables then delete the pod.
71
+
62
72
## Step 2: Test if the changes were applied correctly
63
73
64
74
In order to check if the Inotify value has been changed properly, you can escalate a shell into a pod :
0 commit comments