What would you like to be added:
I would like to be able to add tasks to the TinkerBellTemplateConfig without having to take ownership of the entire TinkerbellTemplateConfig. Currently the workflow is full of sha values and versions I do not want to be responsible for. Currently, I have to become responsible for every sha and version in the file if all I want to do is add an NTP configuration task.
Why is this needed:
The current template is too much responsibility when I want to add a workflow task.
Also, getting the current template is not documented. It is expected to get it from the bootstrap cluster with kind get wf but that is not documented. Many folks are inclined to copy and paste the config from here, but it is very out of date.
What would you like to be added: I would like to be able to add tasks to the TinkerBellTemplateConfig without having to take ownership of the entire TinkerbellTemplateConfig. Currently the workflow is full of sha values and versions I do not want to be responsible for. Currently, I have to become responsible for every sha and version in the file if all I want to do is add an NTP configuration task.
Why is this needed: The current template is too much responsibility when I want to add a workflow task.
Also, getting the current template is not documented. It is expected to get it from the bootstrap cluster with
kind get wf
but that is not documented. Many folks are inclined to copy and paste the config from here, but it is very out of date.