docs(k8s): update wording

bene2k1 · bene2k1 · commit 93dda5d70463 · 2025-09-30T17:47:34.000+02:00
diff --git a/changelog/august2025/2025-08-27-kubernetes-added-dns-service-ip-and-pod-and-service-cid.mdx b/changelog/august2025/2025-08-27-kubernetes-added-dns-service-ip-and-pod-and-service-cid.mdx
@@ -8,6 +8,6 @@ product: kubernetes
 
 The following parameters can be set when creating a cluster:
 - `service-dns-ip`: IP used for the DNS Service (cannot be changed later)
-- `Pod-cidr`: Subnet used for the Pod CIDR (cannot be changed later)
+- `pod-cidr`: Subnet used for the Pod CIDR (cannot be changed later)
 - `service-cidr`: Subnet used for the Service CIDR (cannot be changed later)
 
diff --git a/pages/cockpit/api-cli/querying-logs-with-logcli.mdx b/pages/cockpit/api-cli/querying-logs-with-logcli.mdx
@@ -74,11 +74,11 @@ An output similar to the following should display:
     2024-05-22T17:33:04+02:00 {component="kapsule-autoscaler"} I0522        1 pre_filtering_processor.go:57] Node scw-k8s-sharp-robinson-default-7cefec16593342e should not be processed by cluster autoscaler (no node group config)
     2024-05-22T17:33:04+02:00 {component="kapsule-autoscaler"} I0522        1 pre_filtering_processor.go:57] Node scw-k8s-sharp-robinson-default-bfb90f82c4b949c should not be processed by cluster autoscaler (no node group config)
     2024-05-22T17:33:04+02:00 {component="kapsule-autoscaler"} I0522        1 static_autoscaler.go:492] Calculating unneeded nodes
-    2024-05-22T17:33:04+02:00 {component="kapsule-autoscaler"} I0522        1 static_autoscaler.go:445] No unschedulable Pods
-    2024-05-22T17:33:04+02:00 {component="kapsule-autoscaler"} I0522        1 filter_out_schedulable.go:87] No schedulable Pods
-    2024-05-22T17:33:04+02:00 {component="kapsule-autoscaler"} I0522        1 filter_out_schedulable.go:177] 0 Pods marked as unschedulable can be scheduled.
-    2024-05-22T17:33:04+02:00 {component="kapsule-autoscaler"} I0522        1 filter_out_schedulable.go:176] 0 Pods were kept as unschedulable based on caching
-    2024-05-22T17:33:04+02:00 {component="kapsule-autoscaler"} I0522        1 filter_out_schedulable.go:137] Filtered out 0 Pods using hints
+    2024-05-22T17:33:04+02:00 {component="kapsule-autoscaler"} I0522        1 static_autoscaler.go:445] No unschedulable pods
+    2024-05-22T17:33:04+02:00 {component="kapsule-autoscaler"} I0522        1 filter_out_schedulable.go:87] No schedulable pods
+    2024-05-22T17:33:04+02:00 {component="kapsule-autoscaler"} I0522        1 filter_out_schedulable.go:177] 0 pods marked as unschedulable can be scheduled.
+    2024-05-22T17:33:04+02:00 {component="kapsule-autoscaler"} I0522        1 filter_out_schedulable.go:176] 0 pods were kept as unschedulable based on caching
+    2024-05-22T17:33:04+02:00 {component="kapsule-autoscaler"} I0522        1 filter_out_schedulable.go:137] Filtered out 0 pods using hints
     ```
 
     <Message type="tip">
diff --git a/pages/dedibox-kvm-over-ip/how-to/dell-idrac6.mdx b/pages/dedibox-kvm-over-ip/how-to/dell-idrac6.mdx
@@ -20,7 +20,7 @@ This page shows you how to use [KVM](/dedibox-kvm-over-ip/concepts/#kvm-over-ip)
 <Requirements />
 
 - A Dedibox account logged into the [console](https://console.online.net)
-- Installed [Podman](https://Podman.io/getting-started/installation) on your machine
+- Installed [Podman](https://podman.io/getting-started/installation) on your machine
 - Installed [Java](https://www.java.com/en/download/help/download_options.html) on your local computer
 - A Dedibox server with a Dell iDRAC 6 IPMI interface
 
diff --git a/pages/gpu/how-to/use-mig-with-kubernetes.mdx b/pages/gpu/how-to/use-mig-with-kubernetes.mdx
@@ -34,7 +34,7 @@ In this guide, we will explore the capabilities of NVIDIA MIG within a Kubernete
 
 1. Find the name of the Pods running the Nvidia Driver:
     ```
-    % kubectl get Pods -n kube-system
+    % kubectl get pods -n kube-system
     NAME                                                              READY   STATUS      RESTARTS   AGE
     cilium-operator-fbff794f4-kff42                                   1/1     Running     0          4h13m
     cilium-sfkgc                                                      1/1     Running     0          4h12m
@@ -324,14 +324,14 @@ In this guide, we will explore the capabilities of NVIDIA MIG within a Kubernete
 2. Deploy the Pods:
     ```
     % kubectl create -f deploy-mig.yaml
-    Pod/test-1 created
-    Pod/test-2 created
-    Pod/test-3 created
-    Pod/test-4 created
-    Pod/test-5 created
-    Pod/test-6 created
-    Pod/test-7 created
-    Pod/test-8 created
+    pod/test-1 created
+    pod/test-2 created
+    pod/test-3 created
+    pod/test-4 created
+    pod/test-5 created
+    pod/test-6 created
+    pod/test-7 created
+    pod/test-8 created
     ```
 
 3. Display the logs of the Pods. The Pods print their UUID with the `nvidia-smi` command:
diff --git a/pages/kubernetes/api-cli/cluster-monitoring.mdx b/pages/kubernetes/api-cli/cluster-monitoring.mdx
@@ -62,13 +62,13 @@ Deploy the Prometheus stack in a dedicated Kubernetes [namespace](https://kubern
     ```
 4. Verify that the created Pods are all running once the stack is deployed. You can also check whether the 100Gi block volume was created:
     ```bash
-    kubectl get Pods,pv,pvc -n monitoring
+    kubectl get pods,pv,pvc -n monitoring
     NAME                                                READY   STATUS    RESTARTS   AGE
-    Pod/prometheus-alertmanager-6565668c85-5vdxc        2/2     Running   0          67s
-    Pod/prometheus-kube-state-metrics-6756bbbb8-6qs9r   1/1     Running   0          67s
-    Pod/prometheus-node-exporter-fbg6s                  1/1     Running   0          67s
-    Pod/prometheus-pushgateway-6d75c59b7b-6knfd         1/1     Running   0          67s
-    Pod/prometheus-server-556dbfdfb5-rx6nl              1/2     Running   0          67s
+    pod/prometheus-alertmanager-6565668c85-5vdxc        2/2     Running   0          67s
+    pod/prometheus-kube-state-metrics-6756bbbb8-6qs9r   1/1     Running   0          67s
+    pod/prometheus-node-exporter-fbg6s                  1/1     Running   0          67s
+    pod/prometheus-pushgateway-6d75c59b7b-6knfd         1/1     Running   0          67s
+    pod/prometheus-server-556dbfdfb5-rx6nl              1/2     Running   0          67s
 
     NAME                                                        CAPACITY   ACCESS MODES   RECLAIM POLICY   STATUS   CLAIM                                STORAGECLASS   REASON   AGE
     persistentvolume/pvc-5a9def3b-22a1-4545-9adb-72823b899c36   100Gi      RWO            Delete           Bound    monitoring/prometheus-server         scw-bssd                67s
@@ -80,8 +80,8 @@ Deploy the Prometheus stack in a dedicated Kubernetes [namespace](https://kubern
     ```
 5. To access Prometheus use the Kubernetes [port forwarding](https://kubernetes.io/docs/tasks/access-application-cluster/port-forward-access-application-cluster/) feature:
     ```bash
-    export Pod_NAME=$(kubectl get Pods --namespace monitoring -l "app=prometheus,component=server" -o jsonpath="{.items[0].metadata.name}")
-    kubectl --namespace monitoring port-forward $Pod_NAME 9090
+    export pod_NAME=$(kubectl get pods --namespace monitoring -l "app=prometheus,component=server" -o jsonpath="{.items[0].metadata.name}")
+    kubectl --namespace monitoring port-forward $pod_NAME 9090
     ```
 6. Access the Prometheus dashboard using the following URL: [http://localhost:9090](http://localhost:9090)
     <Lightbox image={image} alt="" />
@@ -200,7 +200,7 @@ The `loki` application is not included in the default Helm repositories.
     ```
 5. Now that both Loki and Grafana are installed in the cluster, check if the Pods are correctly running:
     ```bash
-    kubectl get Pods -n loki-stack
+    kubectl get pods -n loki-stack
 
     NAME                            READY   STATUS    RESTARTS   AGE
     loki-grafana-67994589cc-7jq4t   0/1     Running   0          74s
diff --git a/pages/kubernetes/how-to/deploy-image-from-container-registry.mdx b/pages/kubernetes/how-to/deploy-image-from-container-registry.mdx
@@ -157,9 +157,9 @@ To deploy the previously created container image in a Kapsule cluster, you need
     ```bash
     kubectl apply -f deployment.yaml
     ```
-4. Use the `kubectl get Pods` command to check the status of the deployment:
+4. Use the `kubectl get pods` command to check the status of the deployment:
     ```bash
-    kubectl get Pods
+    kubectl get pods
     ```
 
     ```
@@ -170,6 +170,6 @@ To deploy the previously created container image in a Kapsule cluster, you need
 
 As you can see in the output above, the image has been pulled successfully from the registry and two replicas of it are running on the Kapsule cluster.
 
-For more information how to use your Container Registry with Kubernetes, refer to the [official documentation](https://kubernetes.io/docs/tasks/configure-Pod-container/pull-image-private-registry/).
+For more information how to use your Container Registry with Kubernetes, refer to the [official documentation](https://kubernetes.io/docs/tasks/configure-pod-container/pull-image-private-registry/).
 
 
diff --git a/pages/kubernetes/how-to/deploy-x86-arm-images.mdx b/pages/kubernetes/how-to/deploy-x86-arm-images.mdx
@@ -27,7 +27,7 @@ These images contain binaries for multiple architectures, allowing Kubernetes to
 
 1. Build multi-arch images. Docker supports multi-arch builds using `buildx`.
 2. Push the built images to a container registry accessible by your Kubernetes cluster. For example, you can use the [Scaleway Container Registry](/container-registry/quickstart/).
-3. Specify node selectors and affinity. Use either [node selectors](https://kubernetes.io/docs/concepts/scheduling-eviction/assign-Pod-node/#nodeselector) and [affinity rules](https://kubernetes.io/docs/concepts/scheduling-eviction/assign-Pod-node/#affinity-and-anti-affinity) to ensure Pods are scheduled on nodes with compatible architectures.
+3. Specify node selectors and affinity. Use either [node selectors](https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#nodeselector) and [affinity rules](https://kubernetes.io/docs/concepts/scheduling-eviction/assign-pod-node/#affinity-and-anti-affinity) to ensure Pods are scheduled on nodes with compatible architectures.
     <Message type="tip">
       Alternatively, use taints to mark nodes with specific architectures and tolerations to allow Pods to run on those nodes. Refer to the [official Kubernetes documentation](https://kubernetes.io/docs/concepts/scheduling-eviction/taint-and-toleration/) for more information regarding taints and tolerations.
     </Message>
@@ -39,7 +39,7 @@ Below, you can find an example of a Pod configuration with affinity set to targe
 apiVersion: v1
 kind: Pod
 metadata:
-  name: example-Pod-with-affinity
+  name: example-pod-with-affinity
 spec:
   affinity:
     nodeAffinity:
diff --git a/pages/kubernetes/how-to/manage-node-pools.mdx b/pages/kubernetes/how-to/manage-node-pools.mdx
@@ -77,7 +77,7 @@ This documentation provides step-by-step instructions on how to manage Kubernete
    - The `--ignore-daemonsets` flag is used because daemon sets manage Pods across all nodes and will automatically reschedule them.
    - The `--delete-emptydir-data` flag is necessary if your Pods use emptyDir volumes, but use this option carefully as it will delete the data stored in these volumes.
    - Refer to the [official Kubernetes documentation](https://kubernetes.io/docs/tasks/administer-cluster/safely-drain-node/) for further information.
-5. Run `kubectl get Pods -o wide` after draining, to verify that the Pods have been rescheduled to the new node pool.
+5. Run `kubectl get pods -o wide` after draining, to verify that the Pods have been rescheduled to the new node pool.
 6. [Delete the old node pool](#how-to-delete-an-existing-kubernetes-kapsule-node-pool) once you confirm that all workloads are running smoothly on the new node pool.
 
 ## How to delete an existing Kubernetes Kapsule node pool
diff --git a/pages/kubernetes/how-to/monitor-data-plane-with-cockpit.mdx b/pages/kubernetes/how-to/monitor-data-plane-with-cockpit.mdx
@@ -155,11 +155,11 @@ Key points include:
 - **No logs appearing** in Cockpit:
   - Verify that the Promtail Pod is running.
     ```bash
-    kubectl get Pods -n <promtail-namespace>
+    kubectl get pods -n <promtail-namespace>
     ```
   - Inspect Promtail logs for errors.
     ```bash
-    kubectl logs <promtail-Pod-name> -n <promtail-namespace>
+    kubectl logs <promtail-pod-name> -n <promtail-namespace>
     ```
 
 - **High log ingestion cost**:
diff --git a/tutorials/ceph-cluster/index.mdx b/tutorials/ceph-cluster/index.mdx
@@ -33,7 +33,7 @@ This tutorial guides you through deploying a three-node Ceph cluster with a RADO
 2. Install software dependencies on all nodes and the admin machine:
     ```
     sudo apt update
-    sudo apt install -y python3 chrony lvm2 Podman
+    sudo apt install -y python3 chrony lvm2 podman
     sudo systemctl enable chrony
     ```
 
diff --git a/tutorials/deploy-demo-application-kubernetes-kapsule/index.mdx b/tutorials/deploy-demo-application-kubernetes-kapsule/index.mdx
@@ -140,7 +140,7 @@ Deploy the [whoami](https://github.com/traefik/whoami) application (a well-known
 
    ```bash
    kubectl get deployments
-   kubectl get Pods
+   kubectl get pods
    kubectl get services
    ```
 
@@ -261,7 +261,7 @@ Configure [Horizontal Pod Autoscaling (HPA)](https://www.scaleway.com/en/blog/un
 4. Open another terminal and monitor Pod scaling:
 
    ```bash
-   kubectl get Pods -w
+   kubectl get pods -w
    kubectl get hpa -w
    ```
 
diff --git a/tutorials/deploy-saas-application/index.mdx b/tutorials/deploy-saas-application/index.mdx
@@ -295,9 +295,9 @@ Now that everything is set up, you need to write a manifest to deploy your web a
 
     ```
     NAME                                     READY   STATUS    RESTARTS   AGE
-    Pod/awesome-webapp-7252e88462-9vw92   1/1     Running   0          8m
-    Pod/awesome-webapp-7252e88462-wm2br   1/1     Running   0          8m
-    Pod/awesome-webapp-7252e88462-x6rwv   1/1     Running   0          8m
+    pod/awesome-webapp-7252e88462-9vw92   1/1     Running   0          8m
+    pod/awesome-webapp-7252e88462-wm2br   1/1     Running   0          8m
+    pod/awesome-webapp-7252e88462-x6rwv   1/1     Running   0          8m
 
     NAME                                READY   UP-TO-DATE   AVAILABLE   AGE
     deployment.apps/awesome-webapp   3/3     3            3           8m
diff --git a/tutorials/easydeploy-gitlab-runner/index.mdx b/tutorials/easydeploy-gitlab-runner/index.mdx
@@ -57,7 +57,7 @@ This setup enables you to optimize resource utilization, reduce overhead, and en
 10. Click **Deploy Application** to deploy GitLab Runner on your Kubernetes cluster.
 11. Use the following command to verify that the GitLab Runner is installed and running:
     ```bash
-    kubectl get Pods -n <namespace> # replace "<namespace>" with the name of the Kubernetes namespace in which you have installed your GitLab Runner.
+    kubectl get pods -n <namespace> # replace "<namespace>" with the name of the Kubernetes namespace in which you have installed your GitLab Runner.
     ```
     You should see a Pod with a name similar to `gitlab-runner-xxxxxx-xxxxx` in the `Running` state.
 
@@ -80,7 +80,7 @@ Before your GitLab Runner can start executing jobs from your GitLab repository,
    - Connect to your Kubernetes cluster where the GitLab Runner is deployed.
    - Use the following command to start the registration process:
      ```bash
-     kubectl exec -it <gitlab-runner-Pod-name> -- gitlab-runner register
+     kubectl exec -it <gitlab-runner-pod-name> -- gitlab-runner register
      ```
    - When prompted, enter the following details:
      - **GitLab instance URL:** The URL of your GitLab server (e.g., `https://gitlab.com` or your self-hosted GitLab URL).
@@ -137,7 +137,7 @@ Navigate to **CI/CD** > **Pipelines** in your GitLab project to view the status
 <Message type="tip">
   If the pipeline fails, you can check the logs of the GitLab Runner Pod for more information:
    ```bash
-   kubectl logs -n <namespace> <gitlab-runner-Pod-name>
+   kubectl logs -n <namespace> <gitlab-runner-pod-name>
    ```
 </Message>
 
diff --git a/tutorials/easydeploy-vault/index.mdx b/tutorials/easydeploy-vault/index.mdx
@@ -46,7 +46,7 @@ Vault is used to secure, store and protect secrets and other sensitive data usin
 
 1. Check the status of your Vault using the `kubectl` command.
     ```sh
-    kubectl get Pods -l app.kubernetes.io/name=vault
+    kubectl get pods -l app.kubernetes.io/name=vault
     ```
     <Message type="tip">
       If you choose another name for your Vault application ensure to replace the application name with the corresponding value.
diff --git a/tutorials/enabling-encryption-in-kapsule-with-cilium/index.mdx b/tutorials/enabling-encryption-in-kapsule-with-cilium/index.mdx
@@ -73,7 +73,7 @@ After creating the `CiliumNodeConfig`, you must restart Cilium to apply these en
 
 3. Verify the Pod status using the following `kubectl` command:
     ```
-    kubectl get Pods -n kube-system -l k8s-app=cilium
+    kubectl get pods -n kube-system -l k8s-app=cilium
     ```
     All Cilium Pods should eventually show as **Running** and **Ready**.
 
diff --git a/tutorials/get-started-containers-docker/index.mdx b/tutorials/get-started-containers-docker/index.mdx
@@ -31,7 +31,7 @@ Before starting the practical steps of this tutorial, we review a few key concep
 
 * **Container**: A portable package of software that includes its own environment and dependencies (code, runtime, configuration, system libraries) so that it can run on any host system.
 
-* **Docker**: An open-source platform to package applications into containers. As well as building containerized application images, Docker also lets you run them and much more. Alternatives to Docker include [Podman](https://Podman.io/) and [LXC](https://linuxcontainers.org/), though Docker is the market leader and the one we'll be using in this tutorial.
+* **Docker**: An open-source platform to package applications into containers. As well as building containerized application images, Docker also lets you run them and much more. Alternatives to Docker include [Podman](https://podman.io/) and [LXC](https://linuxcontainers.org/), though Docker is the market leader and the one we'll be using in this tutorial.
 
 * **Kubernetes**: An [open source container orchestration platform](https://kubernetes.io/), designed to automate the deployment, scaling, and management of containerized applications.
 
diff --git a/tutorials/get-started-deploy-kapsule/index.mdx b/tutorials/get-started-deploy-kapsule/index.mdx
@@ -162,7 +162,7 @@ Now that we have created our cluster, connected to it with `kubectl`, and define
     ```
 5. Run the following command, replacing the Pod ID with an appropriate output from the previous command, to check that the application is running and listening on a port:
     ```
-    kubectl logs Pod/mydeployment-5599cbcb56-x6lb8
+    kubectl logs pod/mydeployment-5599cbcb56-x6lb8
     ```
 
 ## Exposing the service for testing via NodePort (optional)
diff --git a/tutorials/get-started-kubernetes-storage/index.mdx b/tutorials/get-started-kubernetes-storage/index.mdx
@@ -43,7 +43,7 @@ It is important to differentiate between Kubernetes **system volumes** and **per
 | System volume                            | Persistent volume                          |
 | ---------------------------------------- | ------------------------------------------ |
 | For the k8s system itself                | For applications in the cluster            |
-| Ephemeral (lives and dies with the node) | Persistent (beyond the life of a Pod/node) |
+| Ephemeral (lives and dies with the node) | Persistent (beyond the life of a pod/node) |
 | Auto-created                             | Must be provisioned                        |
 
 You can view your cluster's system volumes in the **Block Storage > Volumes** section of the [console](https://console.scaleway.com/), and see how they are linked to the Instances that make up the nodes of your cluster. However, you should not attempt to use or manage these volumes - leave it to Kubernetes Kapsule.
@@ -184,11 +184,11 @@ Both Deployments and StatefulSets manage the deployment and scaling of a set of
 
     ```
     NAME                READY   STATUS    RESTARTS    AGE
-    Pod/ss-csi-scw-0    1/1     Running   0           63s
-    Pod/ss-csi-scw-1    1/1     Running   0           57s
-    Pod/ss-csi-scw-2    1/1     Running   0           42s
-    Pod/ss-csi-scw-3    1/1     Running   0           32s
-    Pod/ss-csi-scw-4    1/1     Running   0           22s
+    pod/ss-csi-scw-0    1/1     Running   0           63s
+    pod/ss-csi-scw-1    1/1     Running   0           57s
+    pod/ss-csi-scw-2    1/1     Running   0           42s
+    pod/ss-csi-scw-3    1/1     Running   0           32s
+    pod/ss-csi-scw-4    1/1     Running   0           22s
 
 
     NAME                          READY   AGE
diff --git a/tutorials/k8s-kapsule-multi-az/index.mdx b/tutorials/k8s-kapsule-multi-az/index.mdx
@@ -389,7 +389,7 @@ In this configuration, we use the `http_service` block to check that the `ingres
 
 7. Check that your nginx deployment is running and that the Pods are distributed across the different node pools in the different AZs.
     ```
-    kubectl get Pods -n ingress-nginx -o wide
+    kubectl get pods -n ingress-nginx -o wide
 
     NAME                                        READY   STATUS    RESTARTS   AGE   IP             NODE                                             NOMINATED NODE   READINESS GATES
     ingress-nginx-controller-6878d8d4b6-hkq44   1/1     Running   0          30m   100.64.9.233   scw-kapsule-multi-az-pool-fr-par-1-61e22198f8c   <none>           <none>
@@ -605,7 +605,7 @@ It is important to use a storage class with the `volumeBindingMode` option set t
 
 8. Check that the Pods of your Elasticsearch cluster are spread across the different AZs, that your Elasticsarch cluster is healthy, and that Kibana is ready.
     ```
-    kubectl get Pods -n elasticsearch -o wide
+    kubectl get pods -n elasticsearch -o wide
 
     NAME                    READY   STATUS    RESTARTS   AGE     IP             NODE                                             NOMINATED NODE   READINESS GATES
     multi-az-es-default-0   1/1     Running   0          2m40s   100.64.6.118   scw-kapsule-multi-az-pool-fr-par-1-61e22198f8c   <none>           <none>
diff --git a/tutorials/manage-k8s-logging-loki/index.mdx b/tutorials/manage-k8s-logging-loki/index.mdx
diff --git a/tutorials/migrating-docker-workloads-to-kubernetes-kapsule/index.mdx b/tutorials/migrating-docker-workloads-to-kubernetes-kapsule/index.mdx
diff --git a/tutorials/migrating-from-another-managed-kubernetes-service-to-scaleway-kapsule/index.mdx b/tutorials/migrating-from-another-managed-kubernetes-service-to-scaleway-kapsule/index.mdx
diff --git a/tutorials/monitor-k8s-grafana/index.mdx b/tutorials/monitor-k8s-grafana/index.mdx
diff --git a/tutorials/setup-k8s-cluster-rancher/index.mdx b/tutorials/setup-k8s-cluster-rancher/index.mdx
diff --git a/tutorials/traefik-v2-cert-manager/index.mdx b/tutorials/traefik-v2-cert-manager/index.mdx
