Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Provide configuration to allow users to define their own prefixes to sync labels from Machines to Nodes #11657

Open
ykakarap opened this issue Jan 9, 2025 · 1 comment · May be fixed by #11650
Open

Provide configuration to allow users to define their own prefixes to sync labels from Machines to Nodes #11657

ykakarap opened this issue Jan 9, 2025 · 1 comment · May be fixed by #11650
Labels
area/machine Issues or PRs related to machine lifecycle management kind/feature Categorizes issue or PR as related to a new feature. needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@ykakarap
Copy link
Contributor

ykakarap commented Jan 9, 2025

What would you like to be added (User Story)?

As a CAPI user I would like to define the prefixes of labels that should be synced from Machines to Nodes.

Detailed Description

As a user I would like to able to configure the prefixes to determine the labels that CAPI synces from Machines to Nodes.

Anything else you would like to add?

This is a follow-up from the discussion in the community meeting on Dec 11 2024.

Label(s) to be applied

/kind feature
One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.

/area machine
@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. area/machine Issues or PRs related to machine lifecycle management needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Jan 9, 2025
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If CAPI contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@ykakarap ykakarap linked a pull request Jan 9, 2025 that will close this issue
Open
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
area/machine Issues or PRs related to machine lifecycle management kind/feature Categorizes issue or PR as related to a new feature. needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

🌱 sync defined machine labels to node ykakarap/cluster-api
2 participants
@k8s-ci-robot @ykakarap