Deepfactor v2.4 Enhancements Provide Additional Flexibility for Developers Including the Ability to Configure Schema to Derive Application Names, Choose How Pods Can Be Grouped into Apps, More
With the newly released v2.4, we continue the theme of providing flexibility in our Kubernetes admission webhook. These new options will allow customers to configure the webhook to suit their deployment model.
For additional details on v2.4, please review the Release Notes in Deepfactor Docs.
Release Highlights: Continue reading after the matrix to learn more about the latest version of Deepfactor!
- Label-based instrumentation: You can now select the pods in your cluster that you want to instrument with Deepfactor, using label selectors. Read more about how to configure this option here.
- Templatized appName and componentName: In order to provide flexibility to group pods into an application, the Deepfactor webhook now accepts templatized appName and componentName options. Some common values and scenarios have been captured in this article.
- Deepfactor portal installation using Argo CD: If you use Argo CD, you can now use it to install the Deepfactor portal. You can read how to do this here.
- Namespace filter: If you are running your pods in multiple namespaces, you can now filter based on namespace on the Deepfactor UI.
- Performance improvements: We have implemented a series of performance optimizations in v2.4, resulting in significant reduction in the amount of telemetry sent and stored. This should improve not only performance but also the number of concurrent applications the Deepfactor portal can handle.
- TLS termination on external load balancer: If you have already configured a load balancer in your K8s cluster, the Deepfactor portal can use the same.
Visit our Release Notes for more information about our latest releases. And, as always, for those interested in learning more about Deepfactor and the improvements introduced in v2.4, you can request a demo.