Patrician Nodes in Wercker's Kubernetes Architecture

2nd chunk of `content/en/blog/_posts/2016-07-00-Automation-Platform-At-Wercker-With-Kubernetes.md`

e3a7c786e03d72733b92861d8fdf9bfacf114d83a064d5fa000000010000025c

![k8s-architecture.jpg](https://lh5.googleusercontent.com/i_Gtd1J9dekCxy7jJYZDZX0XmAmGD4f8qhrYG60FdVqnM87l-si44BGHjFdEFACZcx2E-rgRZNxuvniYDninlHAl9ZHyF2-jJjKUl-QQH8Au29hwVTbnDc0tP1Rv_Yd8mvt1tfoX)




Patrician nodes are where the bulk of our infrastructure runs. These nodes have appropriate network interfaces to communicate with our backend services as well as be routable by various load balancers. This is where our logging is aggregated and sent off to logging services, our many microservices for reporting and processing the results of job runs, and our many microservices for handling API calls.

Title: Patrician Nodes in Wercker's Kubernetes Architecture

Summary

The text describes the Patrician nodes in Wercker's Kubernetes architecture. These nodes host the bulk of Wercker's infrastructure, including logging aggregation, microservices for processing job results and handling API calls, and have network interfaces to communicate with backend services and load balancers.