Deploy on Ibm Cloud Kubernetes does not install oneagent

[joseafcampos]

Hello All.

I'm deploying dynatrace in IBM Cloud VPC kubernetes following the steps outline in the documentation for full stack observability. 
https://docs.dynatrace.com/docs/shortlink/installation-k8s-cloud-native-fs

I was expecting at the end of deployment to have oneagent installed in all kubernetes nodes like the documentation shows:
> kubectl get pods -n dynatrace
NAME READY STATUS RESTARTS AGE
dynakube-activegate-0 1/1 Running 0 50s
dynakube-oneagent-b88rn 1/1 Running 0 50s
dynakube-oneagent-m5jm4 1/1 Running 0 50s
dynakube-oneagent-qhd9u 1/1 Running 0 50s
dynatrace-oneagent-csi-driver-qxfwx 4/4 Running 0 2m49s
dynatrace-oneagent-csi-driver-xk5c4 4/4 Running 0 2m49s
dynatrace-oneagent-csi-driver-mz6ch 4/4 Running 0 2m49s
dynatrace-operator-7dc8dc7d8c-wmh4z 1/1 Running 0 2m59s
dynatrace-webhook-7bb6957fb5-l8fsq 1/1 Running 0 2m59s
dynatrace-webhook-7bb6957fb5-rqnqk 1/1 Running 0 2m59s

But in my instalation the oneagent in not installed in the nodes as you can see:
xxxxxxx@cloudshell:~$ kubectl get pods -n dynatrace
NAME READY STATUS RESTARTS AGE
cluster-1-activegate-0 1/1 Running 0 74m
dynatrace-oneagent-csi-driver-cdsc9 4/4 Running 0 78m
dynatrace-oneagent-csi-driver-thnqz 4/4 Running 0 78m
dynatrace-oneagent-csi-driver-zjn6k 4/4 Running 0 78m
dynatrace-operator-576c7f8774-l2lhf 1/1 Running 0 27s
dynatrace-webhook-7f898cf489-zzwcd 0/1 Running 0 27s
dynatrace-webhook-97465d54f-5lq9g 1/1 Running 0 78m
dynatrace-webhook-97465d54f-hgfb9 1/1 Running 0 78m

Does anyone has this problem in IBM Cloud or other Cloud platforms?

Thanks.

José Campos

[p_devulapalli]

@joseafcampos Do you see the oneagent daemonset created in your environment?

kubectl get ds/dynatrace-oneagent --namespace=kube-system

[joseafcampos]

Thanks for your reply.

I managed to solve the problem. I followed the new UI Kubernetes instalation, which has a option for IBM Cloud and it worked. I think the problem is the option --set "csidriver.kubeletPath=/var/data/kubelet" that was missing in the helm command: 

helm install dynatrace-operator oci://public.ecr.aws/dynatrace/dynatrace-operator \
--set "csidriver.kubeletPath=/var/data/kubelet" \
--create-namespace \
--namespace dynatrace \
--atomic 

The Dynatrace documentation and the old  interface this option is not present.

https://docs.dynatrace.com/docs/shortlink/installation-k8s-cloud-native-fs#helm

helm install dynatrace-operator oci://public.ecr.aws/dynatrace/dynatrace-operator \
   --create-namespace \
   --namespace dynatrace \
   --atomic \

Now I can see Damonset:
xxxxxxxx@cloudshell:~$ kubectl get ds --all-namespaces
NAMESPACE NAME DESIRED CURRENT READY UP-TO-DATE AVAILABLE NODE SELECTOR AGE
calico-system calico-node 3 3 3 3 3 kubernetes.io/os=linux 36m
dynatrace dynatrace-oneagent-csi-driver 3 3 3 3 3 <none> 18m
dynatrace iks-k8s-2025-04-08-1744141472-oneagent 3 3 3 3 3 <none> 14m
kube-system ibm-vpc-block-csi-node 3 3 3 3 3 <none> 39m
kube-system konnectivity-agent 3 3 3 3 3 <none> 44m
kube-system node-local-dns 0 0 0 0 0 ibm-cloud.kubernetes.io/node-local-dns-enabled=true 44m
kube-system nvidia-driver-installer 0 0 0 0 0 <none> 39m
kube-system nvidia-gpu-device-plugin 0 0 0 0 0 <none> 39m

Thank you.