Skip to content

Node Label Updates Not Propagated to Existing Machines #458

@dgoodwin

Description

@dgoodwin

Not sure if this is expected behavior or not, we allow defining some object metadata for nodes here: https://github.com/kubernetes-sigs/cluster-api/blob/master/pkg/apis/cluster/v1alpha1/machine_types.go#L52

This does mention node "creation" specifically.

Today if you later go edit these labels on a machine set, the changes do not get reflected in pre-existing machines. Only once you delete the machine and wait for a new one to be created will they appear. This means any controller syncing on machines to apply those labels to the node on an on-going basis will not work.

Is this expected? Should node labels be a one time deal or a persistent managed set of labels to apply?

Worth noting if we do support updates, removing one won't work as we can't assume to fully sync the set of labels, other things or the user themselves may be setting labels. It would only be additive, or changing an existing nodes value that would be possible I think.

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