@@ -30,10 +30,10 @@ Here's a brief overview of the main components:
3030Manage the overall state of the cluster:
3131
3232[ kube-apiserver] ( /docs/concepts/architecture/#kube-apiserver )
33- : The core component server that exposes the Kubernetes HTTP API
33+ : The core component server that exposes the Kubernetes HTTP API.
3434
3535[ etcd] ( /docs/concepts/architecture/#etcd )
36- : Consistent and highly-available key value store for all API server data
36+ : Consistent and highly-available key value store for all API server data.
3737
3838[ kube-scheduler] ( /docs/concepts/architecture/#kube-scheduler )
3939: Looks for Pods not yet bound to a node, and assigns each Pod to a suitable node.
@@ -68,16 +68,16 @@ run [systemd](https://systemd.io/) on a Linux node to supervise local components
6868Addons extend the functionality of Kubernetes. A few important examples include:
6969
7070[ DNS] ( /docs/concepts/architecture/#dns )
71- : For cluster-wide DNS resolution
71+ : For cluster-wide DNS resolution.
7272
7373[ Web UI] ( /docs/concepts/architecture/#web-ui-dashboard ) (Dashboard)
74- : For cluster management via a web interface
74+ : For cluster management via a web interface.
7575
7676[ Container Resource Monitoring] ( /docs/concepts/architecture/#container-resource-monitoring )
77- : For collecting and storing container metrics
77+ : For collecting and storing container metrics.
7878
7979[ Cluster-level Logging] ( /docs/concepts/architecture/#cluster-level-logging )
80- : For saving container logs to a central log store
80+ : For saving container logs to a central log store.
8181
8282## Flexibility in Architecture
8383
0 commit comments