aws / aws/eks-anywhere

It is difficult to customize the TinkerbellTemplateConfig

Open
#5,292 4 comments 1 reaction 0 assignees View on GitHub
area/docs area/providers/tinkerbell op2 team/providers triage/accepted
Dominant language
Go
Stars
2.1k
Forks
328
Avg merge
1d 4h
Merged PRs (30d)
9

Description

**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](https://anywhere.eks.amazonaws.com/docs/reference/clusterspec/baremetal/#ubuntu-tinkerbelltemplateconfig-example) 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.

Contributor guide

Open the contributing guide

Research direction

Start with the TinkerbellTemplateConfig definition and the documented Ubuntu TinkerbellTemplateConfig example. Run `kind get wf` on a bootstrap cluster to compare the current workflow with the stale example. Done means users can add a task without owning unrelated SHA values and versions, and the way to retrieve the current template is documented.

Written by the indexing model from the issue text.

Assessment

Tech stack
kubernetes
Domain
documentation, infrastructure
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.