Getting started with Kubernetes experience
To take advantage of the new Kubernetes experience, you can either add new Kubernetes clusters or enable existing Kubernetes clusters for the new experience.
Add new clusters
Start monitoring Kubernetes clusters with Dynatrace.
Enable existing clusters
Enable existing clusters that are already monitored with Kubernetes Classic for the new Kubernetes experience.
Frequently asked questions
What if I don't have DPS or I'm not on the SaaS platform powered by Grail?
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.
Can I still use the old Kubernetes pages after I activate clusters for the new Kubernetes app?
Until further notice, the existing Kubernetes pages (Kubernetes Classic) will still show the data for your Kubernetes clusters.
Do I need to change my rollout with Dynatrace Operator to use the new Kubernetes app?
For the new Kubernetes app, there are (usually) no changes to the rollout required. The minimum requirement is an ActiveGate version 1.279 or higher configured with Kubernetes monitoring 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.
Can I use the new experience for any Kubernetes environment?
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.
What is the impact on my DPS consumption if I monitor my Kubernetes clusters with the new experience?
Any cluster monitored in the new Kubernetes experience will consume your DPS commit based on the Kubernetes Monitoring price ($ per pod-hour) specified on your rate card. The new Kubernetes experience does not use Full-Stack Monitoring or any other capabilities on the DPS rate card.
- If you activate an already monitored Kubernetes cluster from Kubernetes Classic, the Kubernetes monitoring consumption is added on top of the existing license. The classic page is licensed via the rate for Full-Stack Monitoring on any hosts or pods where this is enabled.
If you onboard a new Kubernetes cluster in the app, you are guided to select the observability value you want. If you opt in to application monitoring, you’ll be charged Kubernetes monitoring and Application monitoring, which is based on your price for Full-Stack Monitoring.
If you deactivate the new Kubernetes experience in the settings, consumption of DPS Kubernetes monitoring will stop.