Skip to main content

​
Coverage Matrix

​
Dynatrace Operator Overview

Dynatrace Operator automates deployment and lifecycle management of Dynatrace monitoring components—OneAgent and ActiveGate—within Cloud Native environments. By introducing the DynaKube custom resource, the operator uniformly instruments workloads and nodes, consolidating metrics, logs, and traces. It supports both host-level monitoring through daemonsets and application-level injection directly into pods, eliminating manual instrumentation overhead. Additionally, ActiveGate acts as a local proxy, enabling API monitoring and efficient metrics routing. Overall, Dynatrace Operator provides automated, scalable observability with minimal operational overhead.

​
Chkk Coverage

​
Curated Release Notes

Chkk monitors official Dynatrace Operator release notes, highlighting critical operational changes such as metric renaming, CRD updates, and known upgrade issues. Instead of reviewing all upstream details, Chkk provides targeted summaries specific to your environment. For instance, it alerts you if upcoming releases alter cluster metric dimensions or update DynaKube CRDs requiring configuration adjustments. Chkk also flags known bugs—like past CSI driver termination issues—ensuring proactive remediation. This curated guidance reduces surprises and streamlines operator updates.

​
Preflight & Postflight Checks

Chkk’s preflight checks validate cluster readiness, ensuring compatibility, proper CRD versions, and correct prerequisites (network egress, RBAC, SCC). It identifies deprecated fields in your existing DynaKube resources, preventing configuration mismatches during upgrades. Postflight checks confirm successful upgrades by monitoring operator and component pod health, verifying full OneAgent deployment, and detecting residual issues like orphaned pods. This thorough process maintains consistent monitoring coverage before and after upgrades, significantly reducing operational risk.

​
Version Recommendations

Chkk proactively tracks Dynatrace Operator’s lifecycle, notifying you when versions approach end-of-life or fall behind recommended releases. It provides targeted upgrade suggestions based on stability, community feedback, and Dynatrace’s official support matrix. If your current operator version lacks critical patches or becomes incompatible with newer APIs, Chkk clearly communicates associated risks. Furthermore, Chkk accommodates custom support policies, allowing tailored recommendations aligned with your organization’s needs. This approach ensures you balance upgrade urgency against operational stability.

​
Upgrade Templates

Chkk supplies detailed Upgrade Templates outlining clear, repeatable steps for both in-place and blue-green (canary) upgrade strategies, aligned with Dynatrace best practices. Templates include precise commands, validation checkpoints, and rollback instructions, suitable for GitOps or CI/CD integration. For conservative deployments, blue-green templates guide staged rollouts with built-in rollback points, ensuring minimal disruption. By providing structured upgrade paths, Chkk reduces human error and operational uncertainty, enabling confident, safe operator updates.

​
Preverification

Chkk’s Preverification simulates Dynatrace Operator upgrades in isolated environments to detect potential issues like CRD schema conflicts or resource constraints. It mirrors your existing DynaKube configuration, performing dry-run upgrades and monitoring closely for runtime errors or resource usage spikes. Issues identified—such as stricter CRD validations or RBAC permission changes—are reported before production impact occurs, allowing timely remediation. Preverification significantly reduces upgrade risk by ensuring operational readiness before live deployments.

​
Supported Packages

Chkk seamlessly integrates with all common Dynatrace Operator deployment methods, including Helm, YAML manifests, and OperatorHub installations. It respects your customizations, such as private registry images, tailored RBAC permissions, and specific CRD configurations, ensuring smooth transitions during upgrades. If configurations differ between clusters (e.g., Helm vs. OperatorHub), Chkk consistently supports each scenario without imposing workflow changes. This flexibility ensures operational consistency, minimizing friction across heterogeneous cluster environments.

​
Additional Resources