Self Service Summary
A Kubernetes cluster has remained inactive for an extended period, leading to a problem card. The problem was manually closed, but after some time, another problem was created for the same entity.
| Issue | Solution | Alternative(s) |
| Problem card raised for inactive Kubernetes cluster | Check the connection settings and disable the connection | Contact Dynatrace support if further assistance is needed |
This is an expected behaviour, if the problem itself isn't fixed, a new problem will be raised for that particular entity after 60 days.
In order to avoid multiple alerts raised for an inactive Kubernetes cluster, the connection to it has to be disabled. This can be done by selecting the responsible Kubernetes cluster, opening it's Settings and toggle off the "Enabled".
A last manual closure of the recent problem has to be made, and after this no new problem cards will be generated for this entity.
