But, that kind of power comes with its own challenges ( not just when it comes to monitoring) container orchestration is an inherently complex problem, and requires a control plane like Kubernetes to operate.Īccording to Kubernetes.io, the “various parts of the Kubernetes control plane, such as the Kubernetes Master and kubelet processes, govern how Kubernetes communicates with your cluster.” As the name implies, it controls how Kubernetes interacts with your application it’s responsible for managing the worker nodes, making scheduling decisions and making necessary changes to ensure the cluster gets to a desired state. Kubernetes has made it possible for teams to manage their containerized infrastructure, acting as a common, powerful platform for deploying your applications wherever they run. Containerization was the natural next step in that evolution and - in conjunction with Kubernetes for container orchestration - has reshaped how we build and deploy applications.
We’ve long been relying on microservice-based architecture to ship software faster and more safely. But first, let’s take a look at one of the best modern examples for control planes. In this post, I’ll present an argument for the role of a control plane in monitoring - telling the story of how our users’ need for deep visibility into their applications, and control over their monitoring led us to create a product that provides a monitoring control plane. For a technology to be deemed a control plane, it must manifest all five of these attributes. The control plane is a centralized management interface. So from that, we can derive the five important attributes of a control plane: They go on to describe the management plane as a subset of the control plane and all three planes working in tandem enable programmatic access and - therefore - more flexibility in your organization. Functions of the control plane include system configuration and management” (emphasis mine).
Control packets originate from or are destined for a router. According to TechTarget, “The control plane is the part of a network that carries signaling traffic and is responsible for routing. Hope that helps - pls rate the post if it does.At a high level, a telecommunications architecture contains three basic components: the control plane, the data plane, and the management plane. You could use commands such as the following to get some idea of data traffic flowing through a router: Typically, there isn't a clear demarcation between commands that display control plane info and those that display data plane information. The commands you have on a router that can be used to view control plane operation are as such:
There is no single command that you can use to distinguish between the two. The control plane traffic carries control traffic (which is not end-user data) whereas the data plane traffic is actual end-user data. The data plane is simply an abstraction used to describe the actual flow of data packets using paths determined by the control plane. The information provided by these protocols is then used to building routing/forwarding tables. This includes routing protocols whose job is to communicate information on routes between different routers. The control plane is simply the set of processes that are responsible for disseminating information on routes, labels etc within a network.