Skip to content

Commit ef5ecbb

Browse files
committed
Stabilize scs-0214-v1
Signed-off-by: Matthias Büchse <[email protected]>
1 parent 3274fff commit ef5ecbb

File tree

3 files changed

+4
-17
lines changed

3 files changed

+4
-17
lines changed

Standards/scs-0214-v2-k8s-node-distribution.md

Lines changed: 3 additions & 10 deletions
Original file line numberDiff line numberDiff line change
@@ -1,7 +1,8 @@
11
---
22
title: Kubernetes Node Distribution and Availability
33
type: Standard
4-
status: Draft
4+
status: Stable
5+
stabilized_at: 2024-11-21
56
replaces: scs-0214-v1-k8s-node-distribution.md
67
track: KaaS
78
---
@@ -100,18 +101,10 @@ These labels MUST be kept up to date with the current state of the deployment.
100101
The field gets autopopulated most of the time by either the kubelet or external mechanisms
101102
like the cloud controller.
102103

103-
- `topology.scs.community/host-id`
104-
105-
This is an SCS-specific label; it MUST contain the hostID of the physical machine running
106-
the hypervisor (NOT: the hostID of a virtual machine). Here, the hostID is an arbitrary identifier,
107-
which need not contain the actual hostname, but it should nonetheless be unique to the host.
108-
This helps identify the distribution over underlying physical machines,
109-
which would be masked if VM hostIDs were used.
110-
111104
## Conformance Tests
112105

113106
The script `k8s-node-distribution-check.py` checks the nodes available with a user-provided
114-
kubeconfig file. Based on the labels `topology.scs.community/host-id`,
107+
kubeconfig file. Based on the labels
115108
`topology.kubernetes.io/zone`, `topology.kubernetes.io/region` and `node-role.kubernetes.io/control-plane`,
116109
the script then determines whether the nodes are distributed according to this standard.
117110
If this isn't the case, the script produces an error.

Standards/scs-0214-w1-k8s-node-distribution-implementation-testing.md

Lines changed: 1 addition & 5 deletions
Original file line numberDiff line numberDiff line change
@@ -16,11 +16,7 @@ Worker nodes can also be distributed over "failure zones", but this isn't a requ
1616
Distribution must be shown through labelling, so that users can access these information.
1717

1818
Node distribution metadata is provided through the usage of the labels
19-
`topology.kubernetes.io/region`, `topology.kubernetes.io/zone` and
20-
`topology.scs.community/host-id` respectively.
21-
22-
At the moment, not all labels are set automatically by most K8s cluster utilities, which incurs
23-
additional setup and maintenance costs.
19+
`topology.kubernetes.io/region` and `topology.kubernetes.io/zone`.
2420

2521
## Automated tests
2622

Tests/kaas/k8s-node-distribution/k8s_node_distribution_check.py

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -22,7 +22,6 @@
2222
and does require these labels to be set, but should yield overall pretty
2323
good initial results.
2424
25-
topology.scs.openstack.org/host-id # previously kubernetes.io/hostname
2625
topology.kubernetes.io/zone
2726
topology.kubernetes.io/region
2827
node-role.kubernetes.io/control-plane
@@ -47,7 +46,6 @@
4746
LABELS = (
4847
"topology.kubernetes.io/region",
4948
"topology.kubernetes.io/zone",
50-
"topology.scs.community/host-id",
5149
)
5250

5351
logger = logging.getLogger(__name__)

0 commit comments

Comments
 (0)