Open chrisdoherty4 opened 1 year ago
Needs to take into consideration https://github.com/tinkerbell/tink/issues/198 that claims global timeouts are unsupproted.
Take into consideration removal of the in_use
flag on the Hardware
CRD. Current train of thought is to support a boolean flag indicating the hardware should be netbooted and to strip out in_use
entirely. This necessitates some changed in CAPT as it would then be responsible for determining if a piece of hardware has been provisioned already.
Refactor of Hardware CRD should take into account the removal and/or consolidation of duplicate fields like allowPXE
, allow_pxe
, always_pxe
, allowWorkflow
.
Drop multiple tasks from templates because we no longer support multi-worker workflows. We should explain why tasks are being dropped as part of release notes.
Diskless system support was brought up in the community Slack channel (also at KubeCon NA, actually). Part of that request was to have support for always running a workflow. so, anytime this machine boots up the same workflow would be served. https://cloud-native.slack.com/archives/C01SRB41GMT/p1673924577216179
The design will be re-opened as a PR on the roadmap repository.
Implementation has begun.
A long awaited design has been merged in https://github.com/tinkerbell/roadmap/pull/30
The Custom Resource Definitions defined in the Tink repository are mapped from the old Postgres backend without thinking too much about the data and organization.
We've identified duplicate and hard to understand fields on CRDs. We would like to refactor the CRDs to better represent the data they contain.
Project https://github.com/orgs/tinkerbell/projects/26