OpenShift / k8s cluster upgrade: Dynatrace Operator detecting cordoned nodes and automatic Maintenance Windows ?

[gilles_tabary]

Hello all.

We use Dynatrace Managed + Dynatrace OpenShift operator cloud-native full-stack.

When we upgrade / update an OpenShift / K8S cluster, OpenShift nodes (==VM) goes into cordoned state. OpenShift sets up automatically a kind of OpenShift maintenance mode ( =~ alerts silenced) on each node, in turn.

Is there anything in Dynatrace OpenShift operator, which detects this "cordoned " state and subsequently handles Dynatrace Maintenance Window ? I feel there should be. How do people do to set up these maintenance ?

Regards.

Gilles

[gilles_tabary]

Hi.

I did not find doc nor forums entries on that. Not much fortune with Google either. So here is my take on this.

AutoTag ocpmaintenance : Set (and unset) automatically on Kubernetes Nodes « marqued » Cordoned, and related hosts and daemonset workloads

o Entities matching type(KUBERNETES_NODE),kubernetesNodeCordoned(true)
o Entities matching type(HOST),toRelationships.isNodeOfHost(type("KUBERNETES_NODE"),kubernetesNodeCordoned(true))
o Entities matching type(CLOUD_APPLICATION),cloudApplicationDeploymentTypes(KUBERNETES_DAEMON_SET),toRelationships.isInstanceOf(type(CLOUD_APPLICATION_INSTANCE),fromRelationships.runsOn(type("KUBERNETES_NODE"),kubernetesNodeCordoned(true)))

+ Maintenance Window including « ocpmaintenance » tagged entities

o Filter by Host, tagged ocpmaintenance
o Filter by Kubernetes node, tagged ocpmaintenance
o Filter by Kubernetes workload, tagged  ocpmaintenance

Any one would have a feed-back or prior experience ? Any comments ?

Regards.