Skip to content

Commit 479085c

Browse files
committed
Updating guide
1 parent db75fb6 commit 479085c

File tree

1 file changed

+10
-0
lines changed
  • pages/public_cloud/containers_orchestration/managed_kubernetes/configuring-sysctl-parameters-on-nodes-on-an-ovh-managed-kubernetes-cluster

1 file changed

+10
-0
lines changed

pages/public_cloud/containers_orchestration/managed_kubernetes/configuring-sysctl-parameters-on-nodes-on-an-ovh-managed-kubernetes-cluster/guide.fr-fr.md

Lines changed: 10 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -59,6 +59,16 @@ And define the value of the sysctl key ```fs.inotify.max_user_watches``` based o
5959

6060
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.
6161

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+
6272
## Step 2: Test if the changes were applied correctly
6373

6474
In order to check if the Inotify value has been changed properly, you can escalate a shell into a pod :

0 commit comments

Comments
 (0)