init

A common theme throughout the design of Talos is minimalism. We believe strongly in the UNIX philosophy that each program should do one job well. The init included in Talos is one example of this.

We wanted to create a focused init that had one job - run Kubernetes. There simply is no mechanism in place to do anything else.

To accomplish this, we must address real world operations needs like:

  • Orchestration around creating a highly available control plane
  • Log retrieval
  • Restarting system services
  • Rebooting a node
  • and more

In the following sections we will take a closer look at how these needs are addressed, and how services managed by init are designed to enhance the Kubernetes experience.