UNCLASSIFIED

"development/README.md" did not exist on "development"
README.md 938 Bytes
Newer Older
Vickie Shen's avatar
Vickie Shen committed
1
## Introduction to calico/node
Vickie Shen's avatar
Vickie Shen committed
2

Vickie Shen's avatar
Vickie Shen committed
3
The calico/node container is deployed to every node (on Kubernetes, by a DaemonSet), and runs three daemons:
Vickie Shen's avatar
Vickie Shen committed
4

Vickie Shen's avatar
Vickie Shen committed
5 6 7
- Felix, the Calico daemon that runs on every node and provides endpoints.
- BIRD, the BGP daemon that distributes routing information to other nodes.
- confd, a daemon that watches the Calico datastore for config changes and updates BIRD’s config files.
Vickie Shen's avatar
Vickie Shen committed
8

Vickie Shen's avatar
Vickie Shen committed
9
For manifest-based installations, calico/node is primarily configured through environment variables, typically set in the deployment manifest. Individual nodes may also be updated through the Node custom resource. calico/node can also be configured through the Calico Operator.
Vickie Shen's avatar
Vickie Shen committed
10

Vickie Shen's avatar
Vickie Shen committed
11
## Documentation
Vickie Shen's avatar
Vickie Shen committed
12

Vickie Shen's avatar
Vickie Shen committed
13 14
To learn more about Calico and the calico/node container, see the documentation on [docs.projectcalico.org](https://docs.projectcalico.org).
For calico/node configuration, [here](https://docs.projectcalico.org/reference/node/configuration).