mirror of
https://github.com/siderolabs/talos.git
synced 2025-08-21 06:31:11 +02:00
This is widely considered best practice, we should enforce it. Signed-off-by: Andrew Rynhard <andrew@andrewrynhard.com>
30 lines
969 B
Markdown
30 lines
969 B
Markdown
---
|
|
title: "init"
|
|
date: 2018-10-29T19:40:55-07:00
|
|
draft: false
|
|
weight: 20
|
|
menu:
|
|
docs:
|
|
parent: 'components'
|
|
weight: 20
|
|
---
|
|
|
|
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.
|
|
To that extent, `init` is relatively static in that it does not allow for arbitrary user defined services.
|
|
Only the services necessary to run Kubernetes and manage the node are available.
|
|
This includes:
|
|
|
|
- [containerd](/docs/components/containerd)
|
|
- [kubeadm](/docs/components/kubeadm)
|
|
- [kubelet](https://kubernetes.io/docs/concepts/overview/components/)
|
|
- [networkd](/docs/components/networkd)
|
|
- [ntpd](/docs/components/ntpd)
|
|
- [osd](/docs/components/osd)
|
|
- [proxyd](/docs/components/proxyd)
|
|
- [trustd](/docs/components/trustd)
|
|
- [udevd](/docs/components/udevd)
|