Dynatrace Operator v1.6.0 availability problems potentially raised for graceful Kubernetes shutdown events

Customers using operation v1.6.0 may see false positive problems/alerts when Kubernetes Nodes are scaling or marked as deleted. We will continue to provide updates as we investigate this issue.

As we continue to investigate the root cause, a workaround for this issue is to downgrade the Dynatrace operator to v1.5.1.

If you need additional support or help, please open a support ticket. We will have an update within the next 24 hours.

We're finalizing the build for a fix in Dynatrace Operator versions v1.6.3 and v1.7.1 to address the issue impacting availability events.

If you're currently affected, we recommend temporarily downgrading to Operator version v1.5.1 as a workaround.

For full details and ongoing updates, please refer to the Dynatrace Community post:
https://community.dynatrace.com/t5/Heads-up-from-Dynatrace/False-positive-availability-events-are-triggered-for-Kubernetes/ta-p/286453

We have completed rollout of the Dynatrace Operator v1.6.3 and v1.7.1 to GitHub. For the RedHat Marketplace release we are still in the process of rolling out the above versions.
We are also in the process of updating our release notes for the above releases.
Thank you for your patience, and we apologize for any inconvenience caused.

We’ve successfully completed the rollout of Dynatrace Operator versions v1.6.3 and v1.7.1 to both GitHub and the RedHat Marketplace. Deployment to the Operator Hub is still underway.

You can find detailed release notes at the following link:
https://docs.dynatrace.com/docs/whats-new/dynatrace-operator

Thank you for your continued patience. We apologize for any inconvenience this may have caused.