Open chrisdoherty4 opened 1 year ago
Initial suggestion is to implement webhooks. Webhooks will give us an opportunity to identify duplicate MAC addresses and IP configurations as well as default any state the user shouldn't need to care about on first submission of Hardware.
https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/
We're going to couple this with #14 but will maintain this ticket for independent tracking.
Tinkerbells primary backend is Kubernetes. This means it acts as the data source for Hardware, Workflows and Templates. When these objects are submitted to the cluster they do not undergo any validation. This theme of work is to address general issues encountered by users when submitting data to Tinkerbell.
Project (Combined with CRD Refactor) https://github.com/orgs/tinkerbell/projects/26
Related https://github.com/tinkerbell/tink/issues/532