Skip to content

Commit 9eb61e7

Browse files
committed
Merge branch 'int-fix-feedback-kube-20250924' of https://github.com/scaleway/docs-content into int-fix-feedback-kube-20250924
2 parents 36c5635 + df7fe2d commit 9eb61e7

File tree

2 files changed

+7
-7
lines changed

2 files changed

+7
-7
lines changed

pages/kubernetes/reference-content/introduction-to-kubernetes.mdx

Lines changed: 6 additions & 6 deletions
Original file line numberDiff line numberDiff line change
@@ -119,10 +119,10 @@ A **service** is an abstraction which defines a logical group of Pods that perfo
119119

120120
By default, services are only available using internally routable IP addresses, but can be exposed publicly.
121121

122-
It can be done either by using the `NodePort` configuration, which works by opening a static port on each node's external networking interface. Otherwise, it is possible to use the `LoadBalancer` service, which creates an Scaleway Load Balancer using Kubernetes load-balancer integration, provided by the CCM.
122+
It can be done either by using the `NodePort` configuration, which works by opening a static port on each node's external networking interface, or the `LoadBalancer` service, which creates a Scaleway Load Balancer using the Kubernetes load-balancer integration, provided by the CCM.
123123

124124
<Message type="note">
125-
To use `NodePort` with Kubernetes Kapsule or Kosmos, security groups for Scaleway Instances must be configured to allow external connections to the exposed ports of the nodes.
125+
To use `NodePort` with Kubernetes Kapsule or Kosmos, you must configure security groups for Scaleway Instances to allow external connections to the exposed ports of the nodes.
126126
</Message>
127127

128128
### ReplicaSet
@@ -135,17 +135,17 @@ However, `Deployments` are a higher-level concept managing ReplicaSets and provi
135135

136136
### Deployments
137137

138-
A `Deployment` in Kubernetes provides declarative updates for applications. It manages `ReplicaSets`, which in turn manage the actual Pods.
138+
A `Deployment` in Kubernetes provides declarative updates for applications. It manages `ReplicaSets`, which in turn manage the actual pods.
139139

140-
The deployment controller continuously ensures that the desired number of Pod replicas are running. If Pods fail, become unresponsive, or are deleted, it automatically creates replacements to match the desired state. Deployments also support rolling updates and rollbacks, making them the standard way to manage stateless applications.
140+
The deployment controller continuously ensures that the desired number of pod replicas are running. If pods fail, become unresponsive, or are deleted, it automatically creates replacements to match the desired state. Deployments also support rolling updates and rollbacks, making them the standard way to manage stateless applications.
141141

142142
### StatefulSets
143143

144-
A `StatefulSet` manages Pods in a similar way to a Deployment, but with one crucial difference: each Pod has a **persistent identity** and is **not interchangeable**. Pods are created from the same specification, yet each one gets a unique, ordinal-based name that persists even if the Pod is rescheduled to a different node.
144+
A `StatefulSet` manages pods in a similar way to a deployment, but with one crucial difference: each pod has a **persistent identity** and is **not interchangeable**. Pods are created from the same specification, yet each one gets a unique, ordinal-based name that persists even if the pod is rescheduled to a different node.
145145

146146
Like other controllers, the StatefulSet controller continuously reconciles the cluster’s actual state with the desired state defined in the StatefulSet object.
147147

148-
Because Pods are treated as unique, each can be associated with its own dedicated storage volume. This makes StatefulSets the preferred choice for workloads that require **stable network identities, persistent storage, and ordered deployment or scaling** such as databases and distributed systems.
148+
Because pods are treated as unique, each can be associated with its own dedicated storage volume. This makes StatefulSets the preferred choice for workloads that require **stable network identities, persistent storage, and ordered deployment or scaling**, such as databases and distributed systems.
149149

150150
### DaemonSets
151151

pages/kubernetes/reference-content/understanding-differences-kapsule-kosmos.mdx

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -44,7 +44,7 @@ Kosmos is Scaleway's **multi-cloud Kubernetes solution**, designed to operate ac
4444
| Auto healing | ✔️ | Scaleway Instances only |
4545
| Auto scaling | ✔️ | Scaleway Instances only |
4646
| Container Storage Interface | ✔️ Persistent volumes (Block Storage) on Scaleway Instances | Scaleway Instances only |
47-
| Free mutualized basic control plane | ✔️ | ✔️ |
47+
| Free mutualized control plane | ✔️ | ✔️ |
4848
| Dedicated control plane options | ✔️ | ✔️ |
4949
| Scaleway VPC | ✔️ Controlled isolation or full isolation | ✘ No integration |
5050
| Scaleway Cockpit | ✔️ | ✔️ |

0 commit comments

Comments
 (0)