Channels
academy
amazon
arm
azure
cabpr
chinese
ci-cd
danish
deutsch
developer
elemental
epinio
espanol
events
extensions
fleet
français
gcp
general
harvester
harvester-dev
hobbyfarm
hypper
japanese
k3d
k3os
k3s
k3s-contributor
kim
kubernetes
kubewarden
lima
logging
longhorn-dev
longhorn-storage
masterclass
mesos
mexico
nederlands
neuvector-security
office-hours
one-point-x
onlinemeetup
onlinetraining
opni
os
ozt
phillydotnet
portugues
rancher-desktop
rancher-extensions
rancher-setup
rancher-wrangler
random
rfed_ara
rio
rke
rke2
russian
s3gw
service-mesh
storage
submariner
supermicro-sixsq
swarm
terraform-controller
terraform-provider-rancher2
terraform-provider-rke
theranchcast
training-0110
training-0124
training-0131
training-0207
training-0214
training-1220
ukranian
v16-v21-migration
vsphere
windows
Powered by
Title
g
great-photographer-94826
01/12/2023, 11:38 AM
Hi! Based on the Longhorn documentation (
https://longhorn.io/docs/1.4.0/volumes-and-nodes/scheduling/#the-node-and-zone-selection-stage
), I understand that it is possible for Longhorn to create replicas by creating replicas of a volume so that they are placed on separate sites. For example, if I'm using a three-sites design, with a setting of "defaultClassReplicaCount: 3", each site will have one replica. My question is, how can I tell Longhorn which node belongs to which site? Can the Kubernetes zone tag (
https://kubernetes.io/docs/reference/labels-annotations-taints/#topologykubernetesiozone
) be suitable for this, or does it need to be used in a separate tag for Longhorn?
✅ 1
It's work with "
topology.kubernetes.io/zone
" label.
👍 2
2 Views
#longhorn-storage
Join Slack