-
The Tinkerbell stack is a set of containers that could be managed by a Kubernetes operator. Initial stack deployment is reasonably trivial but it becomes more complex with stack upgrades. We have seen…
-
-
**What happened**:
I'm creating a EKS anywhere cluster for bare metal
After the action "stream-image" (the image is ubuntu 20.04 EFI), fdisk shows 2 partitions, /dev/sda1 and /dev/sda2 (tota…
-
I think I have all the badges for the Labyrinth (Issue 28) on TinkerBell on Homecoming/Reunion. Can I help by adding JSON files for those? Or can I take a stab at it and send it to one of you folks wi…
-
When deploy EKSA on KVM machines with Tinkerbell, disk is marked as /dev/vda in [hardware.csv](https://anywhere.eks.amazonaws.com/docs/reference/baremetal/bare-preparation/#disk).
The Tinkerbell a…
-
Significant architectural changes have happened to Tinkerbell in the last 12 months; the documentation does not reflect these changes.
To minimize documentation effort we want the following:
1. …
-
Happens with Lyapunov
![Lyapunov Tinkerbell map IC(-0 720,-0 640) Parameter range(-0 600,-0 200) Divisions 5000 Parameter(s)(0 900,2 000,0 500) Iterations 150](https://github.com/maximestapelle/Cha…
-
Currently, Workflows have to be created using a 1:1 mapping between Hardware and Workflow. This has been the case since the beginning. Workflow creation is left up to the user. For large deployments t…
-
I setup a Cluster API environment with Tinkerbell provider, plus a tinkerbell stack on a single server by following this https://github.com/tinkerbell/cluster-api-provider-tinkerbell/tree/main/docs.…
-
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 validati…