1KUBERNETES(1)(kubernetes) KUBERNETES(1)(kubernetes)
2
3
4
5Eric Paris Jan 2015
6
7
9 kubelet -
10
11
12
14 kubelet [OPTIONS]
15
16
17
19 The kubelet is the primary "node agent" that runs on each node. It can
20 register the node with the apiserver using one of: the hostname; a flag
21 to override the hostname; or specific logic for a cloud provider.
22
23
24 The kubelet works in terms of a PodSpec. A PodSpec is a YAML or JSON
25 object that describes a pod. The kubelet takes a set of PodSpecs that
26 are provided through various mechanisms (primarily through the apis‐
27 erver) and ensures that the containers described in those PodSpecs are
28 running and healthy. The kubelet doesn't manage containers which were
29 not created by Kubernetes.
30
31
32 Other than from an PodSpec from the apiserver, there are three ways
33 that a container manifest can be provided to the Kubelet.
34
35
36 File: Path passed as a flag on the command line. Files under this path
37 will be monitored periodically for updates. The monitoring period is
38 20s by default and is configurable via a flag.
39
40
41 HTTP endpoint: HTTP endpoint passed as a parameter on the command line.
42 This endpoint is checked every 20 seconds (also configurable with a
43 flag).
44
45
46 HTTP server: The kubelet can also listen for HTTP and respond to a sim‐
47 ple API (underspec'd currently) to submit a new manifest.
48
49
50
52 --azure-container-registry-config="" Path to the file containing
53 Azure container registry configuration information.
54
55
56 --log-flush-frequency=5s Maximum number of seconds between log
57 flushes
58
59
60 --version=false Print version information and quit
61
62
63
65 January 2015, Originally compiled by Eric Paris (eparis at redhat dot
66 com) based on the kubernetes source material, but hopefully they have
67 been automatically generated since!
68
69
70
71Manuals User KUBERNETES(1)(kubernetes)