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: docs/README.md
+4-3Lines changed: 4 additions & 3 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -39,23 +39,24 @@ More details on the [cloud-controller role](https://kubernetes.io/docs/concepts/
39
39
40
40
### Features
41
41
- Node controller: manages nodes and node metadata,
42
-
- Service controller: allows creation of LoadBalancer services, based on [Load Balancer Units (LBU)](https://docs.outscale.com/en/userguide/About-Load-Balancers.html).
42
+
- Service controller: allows creation of LoadBalancer services, based on [Load Balancer Units (LBU)](https://docs.outscale.com/en/userguide/About-Load-Balancers.html),
43
+
- Node labeler: a separate binary that can be executed on nodes to add cluster/physical host server labels on nodes ([see example](../examples/node-labels/README.md))
43
44
44
45
---
45
46
46
47
## ⚙ Installation
47
48
48
49
### Kubernetes version support
49
50
50
-
Each Kubernetes version requires a specific CCM version.
51
+
Each CCM version targets a specific Kubernetes version. It is recommended to run the CCM version matching your Kubernetes version, but higher versions are expected to work.
51
52
52
53
CCM versions use the same major and minor version numbers as their corresponding Kubernetes releases. Patch version numbering is specific to the Outscale CCM and does not match Kubernetes patch releases.
53
54
54
55
E.g. Kubernetes v1.32.x will need CCM v1.32.y.
55
56
56
57
CCM v0.2.8 can be safely used with Kubernetes 1.30.x, and CCM v1.0.x can be safely used with Kubernetes 1.32.x.
57
58
58
-
CCM versions are available for Kubernetes 1.31, 1.32, and 1.33. As Kubernetes 1.31 has reached end of life (EOL), CCM v1.31 releases will be discontinued in the near future. Support for Kubernetes 1.34 will be added soon.
59
+
CCM versions will be released for Kubernetes 1.32, 1.32, 1.33 and 1.34. As Kubernetes 1.31 has reached its end of life (EOL), no CCM releases are planned. In case of a critical issue with CCM v1.31.3, the latest CCM version for 1.32 may be used instead.
This example shows how to label nodes with the following topology labels:
4
+
*`topology.outscale.com/cluster`
5
+
*`topology.outscale.com/server`
6
+
7
+
This allows deployments scenarios where:
8
+
* latency is critical, and pods should be deployed in the same cluster/on the same server,
9
+
* redundancy is critical, and pods should be deployed in different clusters/on different servers.
10
+
11
+
It is expected that nodes are deployed using [attract/repulse placement contraints](https://docs.outscale.com/en/userguide/Configuring-a-VM-with-User-Data-and-OUTSCALE-Tags.html#_adding_outscale_tags_in_user_data).
kubectl get nodes -o custom-columns=NAME:.metadata.name,CLUSTER:.metadata.labels.topology\\.outscale\\.com/cluster,SERVER:.metadata.labels.topology\\.outscale\\.com/server
0 commit comments