There are only 12 binaries in Talos Linux

Re:There are only 12 binaries in Talos Linux by wmf on Monday March 04, 2024 @03:10PM (#39595378)

Where is networking configured? I assume the system has to have an IP address before containerd can fetch images.

[ Parent | on HN ]

Re:There are only 12 binaries in Talos Linux by JustinGarrison on Monday March 04, 2024 @03:30PM (#39595626)

Everything is API driven and static networking can be configured via kernel args

https://www.talos.dev/latest/reference/configuration/v1alpha...

[ Parent | on HN ]

Re:There are only 12 binaries in Talos Linux by burnte on Monday March 04, 2024 @03:42PM (#39595774)

DHCP I would assume.

[ Parent | on HN ]

Re:There are only 12 binaries in Talos Linux by wmf on Monday March 04, 2024 @03:46PM (#39595822)

Yeah but where is the DHCP client? In the kernel?

[ Parent | on HN ]

Re:There are only 12 binaries in Talos Linux by andrewrynhard on Monday March 04, 2024 @04:00PM (#39596029)

In machined (PID1 of Talos).

[ Parent | on HN ]

Re:There are only 12 binaries in Talos Linux by funcDropShadow on Tuesday March 05, 2024 @02:45AM (#39600468)

And moving a network protocol implementation into PID1 is good why? So any security vulnerability in the DHCP implementation gives you root.

[ Parent | on HN ]

Re:There are only 12 binaries in Talos Linux by birdiesanders on Monday March 04, 2024 @11:07PM (#39599325)

You use machineConfigs that are used to provision the base OS and configure it, and the clusterConfig is used to bootstrap k8s on those machines. You can make subtypes and super types, you can have different networking setups, whatever you like, just apply and the OS is driven to state, then k8s is brought up from there. You are presented a kubeconfig after. Changes are done via application of updated machineConfig. Works great in practices and if you write an operator you can manage the config generation via k8s manifests and get wild with it.

[ Parent | on HN ]