topic Re: Kubernetes injection was not configured for this process in Container platforms

Kubernetes injection was not configured for this process

henk_stobbe — Tue, 11 Jun 2024 19:08:14 GMT

Hello,

Anybody know what Dt means by below message?

It is a ngnix process.

Re: Kubernetes injection was not configured for this process

DanielS — Tue, 11 Jun 2024 20:39:40 GMT

Hello @henk_stobbe Could you please check if you have something of the type DO NOT MONITOR configured here:

regarding NGINX pods?

Re: Kubernetes injection was not configured for this process

henk_stobbe — Tue, 11 Jun 2024 20:51:28 GMT

Hallo Daniel,

Thanks for your reply, to be honest I did not check. But I am lucky (-;

Again thank you!

Re: Kubernetes injection was not configured for this process

erh_inetum — Wed, 12 Jun 2024 04:55:18 GMT

Hi @henk_stobbe

I confirm you that Container Monitoring Rules disable processes injection as Daniel says. We've configured some rules here and it's disabled the deep monitoring in the processes running in the namespaces that match with the rules.

But in our case, Kubernetes is on cloudNativeFullStack and it shouldn´t apply the rules:

But it's doing it!

We changed the deployment mode from classicfullstack to cloudnativefullstack.

Maybe this is reason for which the rules continue applying. Does anyone know if this may be the reason?

Regards,

Elena.

Re: Kubernetes injection was not configured for this process

henk_stobbe — Wed, 12 Jun 2024 07:17:22 GMT

Daniel Elena,

Both, thank you for your great tips, but there was one (and wrong) namespace defined in the dynakube.yaml.

My apologies,but still great hints, thanks!

KR Henk

Re: Kubernetes injection was not configured for this process

PedroDeodato — Tue, 18 Jun 2024 11:21:40 GMT

I'm facing the same issue...

We did a fresh installation, with Cloud Native Full Stack, and nearly every application process shows this message: so, no services monitored 😞

We did not have any rule on the environment nor any annotation/label on any Kubernetes entity.

Does anyone know what might be the cause of this and what should we do to ensure that every application pod has deep monitoring??

Thanks!

Re: Kubernetes injection was not configured for this process

Mohamed_Hamdy — Tue, 18 Jun 2024 14:03:41 GMT

Have you validated the deployment? If possible, could you please share the results of the following commands?

kubectl get dynakube -n dynatrace
kubectl get pods -n dynatrace

are you able to see the dynatrace-oneagent-csi-driver?

Please note that both the OneAgent and the CSI driver are deployed as DaemonSets. Therefore, you should have a OneAgent and a CSI driver pod running on each node.

Re: Kubernetes injection was not configured for this process

umeshdt2023 — Mon, 15 Jul 2024 15:07:11 GMT

Any suggestion/recommendation on "Deep monitoring is not active". We are seeing this for all .net/Java/ngix

We installed using cloud native full stack monitoring steps and all Dynatrace pods are running but seeing following message.

Re: Kubernetes injection was not configured for this process

apanoobee — Tue, 13 Aug 2024 09:04:33 GMT

Hi @henk_stobbe - are you able to share which bit in the dynakube yaml file you've seen the error in?

Re: Kubernetes injection was not configured for this process

kalle_lahtinen — Wed, 18 Sep 2024 08:38:52 GMT

Hi @PedroDeodato,

I'm having the precise same issue. Fresh installation using cloudNativeFullStack. On a surface level, the full-stack monitoring seems to be working normally, but then all potential processes which could be deep monitored are seeing this error message. Did you manage to resolve it? Any idea where that "Kubernetes injection was not configured for this process" is coming from?

At least is doesn't appear to be coming from custom process monitoring rules, because then it would specifically say it's disabled due to a rule.

Re: Kubernetes injection was not configured for this process

erh_inetum — Wed, 18 Sep 2024 08:54:21 GMT

Hi @umeshdt2023, @kalle_lahtinen and @PedroDeodato ,

Did you try to lauch this

kubectl label namespace <my_namespace> dynatrace.com/inject=true

Doc: https://docs.dynatrace.com/docs/shortlink/annotate#monitor-specific-namespaces

As far as I know, deep monitoring for Cloud Native Full Stack is not enable at least you specify what namespaces, pods, etc. you want to monitor.

On my experience, I had to do that for having deep monitoring in the namespaces in which we wanted to have deep monitoring.

Hope it helps.

Regards,

Elena.

Re: Kubernetes injection was not configured for this process

kalle_lahtinen — Wed, 18 Sep 2024 09:16:21 GMT

Hi Elena,

At the beginning of that doc it says:

"By default, Dynatrace Operator injects OneAgent into all namespaces, except for:

Namespaces prefixed with kube- or openshift-.
The namespace where Dynatrace Operator was installed."

Therefore we shouldn't have to separately use that config, like it says: "To configure the Dynatrace Operator to inject OneAgent into only certain namespaces".

It sounds like that config can be used if you want to disable the injection for most namespaces, and then only include a handful. But by default we should have everything included (except ones starting with kube- or openshift-).

Re: Kubernetes injection was not configured for this process

PedroDeodato — Wed, 18 Sep 2024 09:45:59 GMT

My interpretation was the same as @kalle_lahtinen ...

But I haven't test this again for a long time... after facing the issue, we tried Classic Full-Stack and it worked like a charm, first try (after restart, obviously). Never tried Cloud Native Full Stack since.

Re: Kubernetes injection was not configured for this process

erh_inetum — Wed, 18 Sep 2024 09:50:10 GMT

Hi Pedro and @kalle_lahtinen ,

Thanks both for your comments.

Yes. I though like you two but we did that I said and got enabling deep monitoring. For that reason I suggested testing that.

Thanks and Regards,

Elena.

Re: Kubernetes injection was not configured for this process

PedroDeodato — Wed, 18 Sep 2024 09:53:25 GMT

Greetings, @kalle_lahtinen !

I also replied above on @erh_inetum 's message, but I'll leave it here also a more detailed description, for reference.

Basically, after several interactions with Dynatrace Chat & Dynatrace Support, we gave up on Cloud Native Full-Stack.

In our case, it was not working as it is unable to instrument namespace that have a label "managedby: aks" (not the actual name of the label, but it was something like that). But our client's namespace did have this labels, purposedly, which could not be removed.

So, facing this dead end, we uninstalled the Cloud Native Full Stack and proceeded with Classic Full Stack.

All we did was install, restart application pods and everything was instrumented right away.

Since then, just to be safe, we have always went straight with Classic Full Stack: it was working great before Cloud Native Full Stack was even the default, and it continues to work great now.

Yes, it does require a restart but it is much easier to deal with customer expectations/unsatisfaction with requesting a restart, rather that having lots of messages that raise questions and services not being instrumented.

Hope this helps!

Re: Kubernetes injection was not configured for this process

Peter_Youssef — Wed, 18 Sep 2024 11:29:31 GMT

Hello @henk_stobbe

Kindly,

first check on the environment level

container monitoring level

ensure cloud application and workload detection is enabled for K8s

ensure onaagent services are configured and Restart is executed

try adding container monitoring rule

update operator version, restart and validate the Process technology is supported or not

https://docs.dynatrace.com/docs/shortlink/section-technology-support#nginx

Thanks.

Re: Kubernetes injection was not configured for this process

rgarzon1 — Tue, 12 Nov 2024 00:07:09 GMT

After trying everything in this thread, we were able to get it to work.

We are using GKE, and after reviewing the following link:

Kubernetes Monitoring Statistics monitoring | Dynatrace Hub

We identified that the Kubernetes API was the issue. We followed these steps:

- Check the control panel IP:

We used the following command to retrieve the Kubernetes control plane information:

https://docs.dynatrace.com/docs/shortlink/how-it-works-k8s#cloud-native-resources

kubectl cluster-info

- The result was:

Kubernetes control plane is running at https://192.168.0.0

- Update Firewall Ingress Rules:

We then added this IP to the ingress rules in the firewall using the following command:

gcloud compute firewall-rules create allow-webhook-api-server \ --direction=INGRESS \ --action=ALLOW \ --rules=tcp:8443,8383,100200,8443 \ --source-ranges=192.168.0.0/8

- Service Restart:

After adding the rules, the webhook service started working again. After rebooting the services, everything resumed functioning properly.

Hope it helps