aws / aws/eks-anywhere

[baremetal] Changes to `TinkerbellDatacenterConfig.spec` do not get used

Open
#9,066 0 comments 2 reactions 0 assignees View on GitHub
area/providers/tinkerbell kind/bug
Dominant language
Go
Stars
2.1k
Forks
328
Avg merge
1d 4h
Merged PRs (30d)
9

Description

**What happened**:
When creating a workload cluster with different values for `TinkerbellDatacenterConfig.spec` than were specified in the creation of the initial management cluster, the values are not getting used. The original values are still used.

https://anywhere.eks.amazonaws.com/docs/getting-started/baremetal/bare-spec/#example-tinkerbelldatacenterconfigspec

**What you expected to happen**:
Changes to `TinkerbellDatacenterConfig.spec` should work.

**How to reproduce it (as minimally and precisely as possible)**:

**Anything else we need to know?**:

**Environment**:
- EKS Anywhere Release:
- EKS Distro Release:

Contributor guide

Open the contributing guide

Research direction

Start with the linked bare-metal TinkerbellDatacenterConfig.spec example and trace how management-cluster values are reused when a workload cluster is created. Reproduce the case with different spec values, then identify the relevant reconciliation entry point and add coverage showing that the workload cluster uses its updated values.

Written by the indexing model from the issue text.

Assessment

Tech stack
go, kubernetes
Domain
infrastructure
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.