Skip to content

Commit e7ec19f

Browse files
authored
Merge pull request #21 from Sh4d1/update_doc
doc: docuement release branches and tags management
2 parents 4c1bd71 + 5b6cbcc commit e7ec19f

File tree

2 files changed

+39
-2
lines changed

2 files changed

+39
-2
lines changed

README.md

Lines changed: 16 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -24,9 +24,23 @@ Currently `scaleway-cloud-controller-manager` currently implements:
2424

2525
## Compatibility matrix
2626

27-
| | K8S 1.14 | K8S 1.15 | K8S 1.16 | K8S 1.17 |
27+
| | K8S 1.15 | K8S 1.16 | K8S 1.17 | K8S 1.18 |
2828
|---------|----------|----------|----------|----------|
29-
| v0.1.x |||||
29+
| v0.1.x | ~ | ~ || ~ |
30+
| v0.18.x | ~ | ~ | ~ ||
31+
32+
- `` fully supported
33+
- `~` some features may not be supported (usually a Kubernetes version mismatch)
34+
35+
### Branches and releases
36+
37+
There is two types of branches:
38+
- `matser` which is the main branch
39+
- `release-x.y` which are the release branches. Each branch is built againt Kubernetes 1.y
40+
41+
Most of the PRs on `master` will be backported to the supported `release-x.y` branches.
42+
43+
Each release will be cut from the `release-x.y` branch, and will be in the form of `x.y.z` where `z` will be the Scaleway Cloud Controller patch version.
3044

3145
## Getting Started
3246

docs/tags.md

Lines changed: 23 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,23 @@
1+
# Tag management
2+
3+
The Scaleway CCM will also sync the tags of the Scaleway Instance to Kubernetes Labels on the nodes.
4+
5+
**When using Scaleway's managed Kubernetes, Kapsule, the tags on the pool will be transformed into tags on the pool's instances, so applying to all Kubernetes nodes of the pool.**
6+
7+
## Labels
8+
9+
In order for a tag to be synced to a label, it needs to be of the form `foo=bar`.
10+
In this case, the Kuebrnetes nodes will have the label `k8s.scaleway.com/foo=bar`.
11+
12+
Once the tag is removed from the instance, it will also be removed as a label on the node.
13+
14+
## Taints
15+
16+
In order for a tag to be synced to a taint, it needs to be of the form `taint=foo:bar:Effect`, where `Effect` is one of `NoExecute`, `NoSchedule` or `PreferNoSchedule`.
17+
In this case, the Kubernetes nodes will have the tain `k8s.scaleway.com/foo=bar` with the effect `Effect`.
18+
19+
Once the tag is removed from the instance, it will also be removed as a taint on the node.
20+
21+
## Special Kubernetes Labels
22+
23+
- `node.kubernetes.io/exclude-from-external-load-balancers` can be set on the Kubernetes nodes if this same value is set as a tag on the instance. It will have the value `managed-by-scaleway-ccm` and will be deleted if deleted from the tags.

0 commit comments

Comments
 (0)