I’m constantly ranting against large layer-2 domains; recently going as far as saying “we don’t really need all that stuff.” Unfortunately, the IP+Ethernet mentality is so deeply ingrained in every networking engineer’s mind that we rarely ever stop to question its validity.
Let’s fix that and start with the fundamental question: What is Layer-2?
Read more ...In previous posts, we talked about running skyDNS and Heapster on your Kubernetes cluster. In this post, I want to talk about the last of the cluster ‘addons’ available today in the Kubernetes repository. This add on is a combination of Fluentd, Elasticsearch, and Kibana that makes a pretty powerful logging aggregation system on top of your Kubernetes cluster. One of the major struggles with any large deployment is logging. Having a central place to aggregate logs makes troubleshooting and analysis considerably easier to do. That being said, let’s jump right into the configuration.
Note: I have an open PR on this addon to make it a little more flexible from a configuration perspective. Namely, I want to be able to specify the port and protocol used by the API server to access the backend service when using the API server as a service proxy. That being said, some of my pod/controller definitions will be different from what you see on GitHub. I’ll point out the differences below when we come across them.
The first step is to have the Kubernetes nodes collect the logs. This is done with a local Fluentd Continue reading
Both companies appear ready to ratchet down their participation in the open source project.