Skip to content

Commit 5f98e58

Browse files
committed
Proofreading
1 parent d03f0cf commit 5f98e58

File tree

1 file changed

+8
-8
lines changed
  • pages/public_cloud/containers_orchestration/managed_kubernetes/configuring-sysctl-parameters-on-nodes

1 file changed

+8
-8
lines changed

pages/public_cloud/containers_orchestration/managed_kubernetes/configuring-sysctl-parameters-on-nodes/guide.en-gb.md

Lines changed: 8 additions & 8 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,7 @@
11
---
2-
title: Adapt your Inotify parameters for your deployments
3-
excerpt: 'Adapt your Inotify parameters for your deployments which needs to have specific Inotify parameters'
4-
updated: 2025-01-09
2+
title: Adapt your Inotify parameters for your Managed Kubernetes Service deployments
3+
excerpt: 'Adapt your Inotify parameters for your deployments which need specific Inotify parameters'
4+
updated: 2025-01-13
55
---
66

77
## Objective
@@ -17,14 +17,14 @@ This guide will cover the modification of the Sysctl parameters which takes in c
1717
- Access to the [OVHcloud Control Panel](/links/manager)
1818
- An OVHcloud Managed Kubernetes cluster
1919
- Access to your OVHcloud Managed Kubernetes cluster through the Kubeconfig file
20-
- You must have the [`kubectl`](https://kubernetes.io/docs/reference/kubectl/overview/){.external} command-line tool installed
20+
- You must have the [kubectl](https://kubernetes.io/docs/reference/kubectl/overview/){.external} command-line tool installed
2121
- Your Kubeconfig is exported into your terminal following this guide : [Configuring Kubectl](/pages/public_cloud/containers_orchestration/managed_kubernetes/configuring-kubectl-on-an-ovh-managed-kubernetes-cluster)
2222

2323
## Instructions
2424

2525
### Step 1: Create a privileged DaemonSet and define the value to modify
2626

27-
Create a YAML named ```sysctl-tuner-daemonset.yaml``` with the content below:
27+
Create a YAML named `sysctl-tuner-daemonset.yaml` with the content below:
2828

2929
```yaml
3030
apiVersion: apps/v1
@@ -55,9 +55,9 @@ spec:
5555
- operator: "Exists" # Allow running on all nodes, including tainted ones
5656
```
5757
58-
And define the value of the sysctl key ```fs.inotify.max_user_watches``` based on your applications' needs.
58+
Define the value of the sysctl key `fs.inotify.max_user_watches` based on your applications' needs.
5959

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

6262
> [!primary]
6363
>
@@ -79,7 +79,7 @@ $ kubectl exec -it <pod> -- cat /proc/sys/fs/inotify/max_user_watches
7979

8080
The output should be the same as the value you defined in the DaemonSet YAML defined above.
8181

82-
Congratulations ! You've successfully modified the maximum Inotify "max_user_watches" value on Managed Kubernetes Service.
82+
Congratulations ! You've successfully modified the maximum Inotify "max_user_watches" value on your Managed Kubernetes Service.
8383

8484
## Go further
8585

0 commit comments

Comments
 (0)