TLDR: Leverage Kubernetes annotations across your cluster to declaratively configure management of monitoring and logging.
Two of the largest surfaces of applications that make contact with infrastructure are monitoring and logging, and this post talks how to approach both these needs in a scalable, composable, and simplified way. If you are familiar with the Kubernetes, Prometheus, Fluentd, and the ELK stack, feel free to skip the background. …
The real power of Kubernetes comes from the API types that describe what pods should look like and manage the scheduling (and querying) of pods. Kubernetes does this with the use of key-value pairs on API objects called Labels. As an example, when a Deployment API-object is created, the Kubernetes Scheduler ensures that a specified number of pods are running across the available servers.
Read more at Medium
