Clarify sharding label management

rancher / fleet

Deploy workloads from Git to large fleets of Kubernetes clusters

https://fleet.rancher.io/

Apache License 2.0

1.47k stars 216 forks source link

Open weyfonk opened 2 months ago

weyfonk commented 2 months ago

Fleet uses two labels for its current sharding implementation:

We should:

[x] clarify how we want to name(space) those labels, making them consistent across Fleet, eg:
- shard.fleet.cattle.io/id=<shard-id>
[x] expose those labels in Fleet's public API, to enable users to consume them.

Note: info on how Flux handles sharding.

Follow-up on #1740.

manno commented 1 month ago

controller label: fleet.cattle.io/shard-id=<shard-id>

sharded resources bear label: fleet.cattle.io/shard-ref=<shard-id>