Exclude cattle-system namespace from Dynatrace monitoring

This document (000020657) is provided subject to the disclaimer at the end of this document.

Environment

The cattle-cluster-agent pod is stuck in a CrashLoopBackOff, logging the following messages:

usage: agent <absolute path of static Go application> [Go application arguments]

Situation

We have observed messages from downstream clusters where the cattle-cluster-agent on any Rancher version can contain no logging outputs, with messages only relating to environment variables.

Running kubectl exec to access a shell on the pod and running /usr/bin/run.sh also produces the error.

Resolution

It is recommend to exclude the cattle-system namespace from being monitored by Dynatrace. The below documentation is specific for Dynatrace, however other solutions could have similar options.

Option 3: https://www.dynatrace.com/support/help/setup-and-configuration/setup-on-container-platforms/kubernetes/get-started-with-kubernetes-monitoring/dto-config-options-k8s#annotate

Cause

Solutions like Dynatrace can potentially inject sidecar containers alongside cattle-cluster-agent/cattle-node-agent containers, causing the agent to exit unpredictably..

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.