Recently, we introduced epsagon-operator for Kubernetes. The operator simplifies the deployment of the agent on Kubernetes clusters.
What are the Kubernetes Operators?
One of the most important value propositions of Kubernetes is automation. However, in the early days of Kubernetes, specific applications required a lot of operational considerations during deployment. For example, lifecycle management of an etcd cluster would require a complex collection of CRDs, services, and stateful sets. With an etcd operator, you don’t have to worry about operating an etcd cluster. The operator manages the clusters and automates tasks related to the management of the cluster. Another benefit of operators is that they enable easy scalability of Kubernetes applications. Operators make use of CRDs to manage applications and their components.
The Epsagon Operator
As more and more applications are being run on Kubernetes, it has become challenging to monitor these containerized applications. Epsagon simplifies this monitoring process by auto-instrumenting applications running on Kubernetes. In addition, trace-based alerts and custom dashboards enable users to achieve complete observability of their Kubernetes environments.
To simplify the process even further, we launched the Epsagon Operator. With the operator, users can easily integrate Epsagon’s agent into their Kubernetes clusters. All you have to do is create a CRD (epsagon-monitoring) and run the commands mentioned in the README. The operator periodically queries the Kubernetes API server to understand and track the state of the custom resource. The operator manages the custom resource for you and is deployed under the deployment name – epsagon-operator-controller-manager. That is it! The Kubernetes clusters are ready to be monitored using Epsagon.
The Epsagon Operator greatly simplifies monitoring Kubernetes environments. Watch this space for more updates to the operator in the near future.