Latest Dynatrace
To take advantage of the new Kubernetes experience, you can either add new Kubernetes clusters or enable existing Kubernetes clusters for the new experience.
Start monitoring Kubernetes clusters with Dynatrace.
Enable existing clusters that are already monitored with Kubernetes Classic for the new Kubernetes experience.
You can’t access the new Kubernetes experience. You can continue to use Kubernetes Classic pages. We continue to support and innovate the existing product, but we encourage you to switch to the new platform to benefit from the latest platform innovations.
If you are already using DPS, reach out to your Dynatrace representative to add pricing for Kubernetes Platform Monitoring to your rate card. Customers who sign their DPS contract after February 2024 will have this capability included by default on their rate card.
Until further notice, the existing Kubernetes pages (Kubernetes Classic) will still be available and show the data for your Kubernetes clusters.
The Kubernetes app doesn't require mandatory changes to the rollout. The minimum requirement is an ActiveGate version 1.279 or higher configured with Kubernetes Platform Monitoring ActiveGate capability. If you use Dynatrace Operator with default configurations (no specific ActiveGate image/tag), the ActiveGate is automatically upgraded, so that you don't need to take action.
You can use the onboarding screen in the Kubernetes app to onboard new clusters. It will always use the latest Dynatrace Operator.
The new Kubernetes app provides valuable insights for all Kubernetes distibutions supported by Dynatrace. There is no difference in supported distributions between the new Kubernetes app and Kubernetes Classic. The new Kubernetes app is optimized for customers with Kubernetes environments ranging up to 12000 pods. This will be increased in future versions of the app.
Users need a set of permissions to read and access relevant data from Grail to use the Kubernetes app. You can find more details about required permissions in the reference section.
Clusters monitored with Kubernetes Platform Monitoring will consume your DPS commit based on the Kubernetes Platform Monitoring price ($ per pod-hour) specified on your rate card.
Clusters monitored with Kubernetes Platform Monitoring and Application observability will consume your DPS commit based on the Kubernetes Platform Monitoring price ($ per pod-hour) and container-based Full-Stack price ($ per GiB-hour of used container memory) specified on your rate card.
Clusters monitored with Kubernetes Platform Monitoring and Full-Stack observability will consume your DPS commit based on the host-based Full-Stack price ($ per GiB-hour of host memory) specified on your rate card.
If you deactivate the new Kubernetes experience in the settings of your cluster, consumption of DPS Kubernetes Platform Monitoring will stop.