Skip to content

ds toplogySpreadConstraints uses a non-existent topologyKey of topology.kubernetes.io/hostname #721

Description

@pearj

I noticed that for the ds toplogySpreadConstraints it uses a non-existent topologyKey of topology.kubernetes.io/hostname.

It instead should be kubernetes.io/hostname.

If you look at the Well-Known Labels, Annotations and Taints, you'll see that for topology.kubernetes.io there are only 2 options, region and zone, but not hostname.

Here are the references I found

Activity

  1. lee-baines commented on Sep 16, 2026

    @lee-baines
    Contributor

    Thanks for highlighting @pearj. We have an ticket to address this

  2. damonconway commented on Oct 2, 2026

    @damonconway
    Contributor

    I have a PR in to fix this. Should be in the next release.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions