monitoring openshift namespace contain Pipeline

[ehanafy]

Hello Dears

did any one monitor open shift cluster that have a running pipeline in namespaces
kubernets v1.25.10+8c21020
operator version 1.2.2

I install the operator on the cluster in classic full stack all pipeline in different namespaces affected and and have problems

[PacoPorro]

If you provide more details about the specific problems you're encountering, maybe we can help you. How are the pipelines being affected? Are there specific error messages or behaviors you're seeing?

Consider reaching out to the Dynatrace support for more specific guidance. They can provide detailed troubleshooting steps.

[ehanafy]

All OpenShift CI/CD pipelines effected and testing  was stopped

openshift team send this errors :
https://access.redhat.com/solutions/6232211

https://access.redhat.com/solutions/6974275

[IzabelaRokita]

Hey @ehanafy, did you manage to find the solution to your problem? If so, it would be amazing if you've shared it with the rest of the Community! If not, let me know, and I'll look for some further assistance 😊

[ehanafy · Accepted solution]

Hey @IzabelaRokita,

We are currently monitoring the Kubernetes cluster using the classic full stack mode. After trying different approaches to monitor the cluster without causing any issues in the pipeline execution, we finally exclude monitoring of namespaces or pods that contain the pipeline (Buildah).

This way, we avoid any interference with the pipeline runs.

in the classic full stack mode you can exclude the name space or pod from the GUI setting by adding rule here (Settings > Processes and containers > Container monitoring rules), but for the cloud  native full stack you will need to configure it through the YAML file 

[IzabelaRokita]

Awesome, glad that you found the working solution! And thanks a lot for sharing it with the rest of our Community 😊 👏