- set up `talos.events.sink` kernel args.
- build and run additional container to receive talos events.
- log all events in the adapter.
Signed-off-by: Artem Chernyshev <artem.chernyshev@talos-systems.com>
Fixes#527
Talos logs (see https://github.com/talos-systems/talos/pull/4600) are
delivered to Sidero over the SideroLink tunnel.
Logs can be seen with:
```
$ kubectl logs -n sidero-system deployment/sidero-controller-manager -c serverlogs -f
{"clock":67194673,"cluster":"management-cluster","facility":"user","machine":"default/management-cluster-cp-4j8f4","metal_machine":"default/management-cluster-cp-hbq57","msg":"[talos] phase bootloader (19/19): done, 176.795226ms\n","priority":"warning","seq":768,"server_uuid":"5b72932a-c482-4aa5-b00e-4b8773d3ac48","talos-level":"warn","talos-time":"2021-11-26T19:34:42.444342392Z"}
```
Logs are annotated on the fly with the information about `Server`,
`MetalMachine`, `Machine` and `Cluster`.
Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
Fixes#615
This implements the SideroLink integration on Sidero side. This feature
requires Talos 0.14 from master as of right now.
SideroLink status is stored in `ServerBinding` resource for each server.
Signed-off-by: Andrey Smirnov <andrey.smirnov@talos-systems.com>
