Today we build upon our existing functionality to provide deeper insight into your Kubernetes workloads from within our Live Containers view, providing a multidimensional look into your Kubernetes environment.
This feature is currently in private beta. If you’d like to register for access, sign up [here_](https://app.datadoghq.com/containers/kubernetes-beta)._
Running Kubernetes applications requires visibility into not only the overall performance of clusters but also the health of individual pods, deployments, and other resources that make up your environment. Datadog already integrates with your containerized environments and includes features like the Live Container view and the Container Map, enabling you to easily monitor Kubernetes and container runtime performance in real time and get deep visibility into clusters.
Today we build upon our existing functionality to provide deeper insight into your Kubernetes workloads from within our Live Containers view, providing a multidimensional look into your Kubernetes environment. Live Containers now offers curated views for your Kubernetes applications, so you can look at performance data in its appropriate context and surface critical information about every layer of your Kubernetes clusters. You can monitor the state of pods or deployments in a specific namespace or availability zone, view the resource specifications for a failed pod within a deployment, correlate node activity with related logs, and more.
Our original Kubernetes tool list was so popular that we've curated another great list of tools to help you improve your functionality with the platform.
This article explains how you can leverage Kubernetes to reduce multi cloud complexities and improve stability, scalability, and velocity.
Get Hands-on experience on Kubernetes and the best comparison of Kubernetes over the DevOps at your place at Kubernetes training
Get Hands-on experience on Kubernetes and the best comparison of Kubernetes over the DevOps at your place at Kubernetes training
Microsoft announced the general availability of Bridge to Kubernetes, formerly known as Local Process with Kubernetes.