orchestrator-kubernetes: make availability-zone node label configurable#36515
Draft
jubrad wants to merge 3 commits into
Draft
orchestrator-kubernetes: make availability-zone node label configurable#36515jubrad wants to merge 3 commits into
jubrad wants to merge 3 commits into
Conversation
Replace the hardcoded `materialize.cloud/availability-zone` label key used for AZ affinity rules with a configurable field, defaulting to the standard `topology.kubernetes.io/zone`. Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
jubrad
force-pushed
the
jubrad/configurable-az-topology-label
branch
from
3e6011b to
d70a016
Compare
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
Alphadelta14
approved these changes
May 12, 2026
| {{- if .Values.availabilityZoneLabel }} | ||
| - "--orchestrator-kubernetes-az-label={{ .Values.availabilityZoneLabel }}" | ||
| {{- else if eq .Values.operator.cloudProvider.type "aws" }} | ||
| - "--orchestrator-kubernetes-az-label=topology.k8s.aws/zone-id" |
Contributor
There was a problem hiding this comment.
this behavior [upstream] upsets me. the non-deterministic zone names are deprecated, so you'd think they could just use the only ones they support.
Contributor
Author
There was a problem hiding this comment.
yeah, it's certainly not ideal, also not ideal that we were taking it to another level.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Two related issues with the Kubernetes orchestrator's AZ scheduling:
materialize.cloud/availability-zone, a proprietary label that only works in Materialize's managed cloud.Solution
Configurable AZ label — Replace the hardcoded label with a configurable field defaulting to the standard
topology.kubernetes.io/zone:mz-orchestrator-kubernetes: newavailability_zone_label: StringonKubernetesOrchestratorConfigenvironmentd: new--orchestrator-kubernetes-az-labelflag (env:ORCHESTRATOR_KUBERNETES_AZ_LABEL), defaulttopology.kubernetes.io/zoneorchestratord: new--orchestrator-kubernetes-az-labelflag; forwarded toenvironmentdavailabilityZoneLabelvalueSupported values:
topology.kubernetes.io/zone(default),topology.k8s.aws/zone-id,materialize.cloud/availability-zone(previous behavior), or any custom label.