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.

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

Make MD metadata available within MachineDeployment Builtins #10836

Closed
srm09 opened this issue Jul 5, 2024 · 1 comment · Fixed by #10837
Closed

Make MD metadata available within MachineDeployment Builtins #10836

srm09 opened this issue Jul 5, 2024 · 1 comment · Fixed by #10837
Assignees
Labels
area/clusterclass Issues or PRs related to clusterclass kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@srm09
Copy link
Contributor

srm09 commented Jul 5, 2024

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

As a runtime extension developer, I'd like to be able to generate bootstrap templates based on metadata set on the machine deployments.

Detailed Description

Cluster topology allows setting additional metadata onto the MachineDeployment. This metadata can be used to add conditional logic when generating patches via runtime extensions. Making this metadata available in the MachineDeployment builtins would allow for easier generation of conditional logic when managing multiple machine deployments per cluster.

Anything else you would like to add?

No response

Label(s) to be applied

/kind feature
/area clusterclass

@k8s-ci-robot k8s-ci-robot added kind/feature Categorizes issue or PR as related to a new feature. area/clusterclass Issues or PRs related to clusterclass 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 Jul 5, 2024
@srm09
Copy link
Contributor Author

srm09 commented Jul 5, 2024

Similar to issue #10823

@fabriziopandini fabriziopandini added priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Jul 8, 2024
@k8s-ci-robot k8s-ci-robot removed 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 Jul 8, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/clusterclass Issues or PRs related to clusterclass kind/feature Categorizes issue or PR as related to a new feature. priority/important-soon Must be staffed and worked on either currently, or very soon, ideally in time for the next release. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants