# Connectivity problem kube-proxy and Oneagent **URL:** \ **Category:** Container platforms\ **Tags:** oneagent, kubernetes\ **Created:** [October 1, 2019, 6:49am UTC](https://community.dynatrace.com/t/connectivity-problem-kube-proxy-and-oneagent/22130 "2019-10-01T06:49:22Z")\ **Posts on this page:** 5\ **Page:** 1
**Author:** ![kamlesh\_a\_verma](https://avatars.discourse-cdn.com/v4/letter/k/8e7dd6/32.png) [@kamlesh\_a\_verma](https://community.dynatrace.com/u/kamlesh_a_verma)\ **Post date:** [October 1, 2019, 6:49am UTC](https://community.dynatrace.com/t/connectivity-problem-kube-proxy-and-oneagent/22130/1 "2019-10-01T06:49:22Z")
I have configured Oneagent on K8S cluster using the following link. > **[GitHub - Dynatrace/dynatrace-oneagent-operator at release-0.4](https://github.com/Dynatrace/dynatrace-oneagent-operator/tree/release-0.4)** > > release-0.4 After configuration, I am seeing an error “kube-proxy kube-proxy (kube-proxy-85qvd):Connectivity problem” under Problem section. Activation of deep monitoring was unsuccessful Monitoring of statically linked Go programs that do not load libc is not supported I understand that kube-proxy unable to communicate on a few ports but I am not seeing any errors in Kube-proxy or dynatrace logs. ---
**Author:** ![gerard\_habchi](https://avatars.discourse-cdn.com/v4/letter/g/439d5e/32.png) [@gerard\_habchi](https://community.dynatrace.com/u/gerard_habchi)\ **Post date:** [October 15, 2019, 12:25am UTC](https://community.dynatrace.com/t/connectivity-problem-kube-proxy-and-oneagent/22130/2 "2019-10-15T00:25:59Z")
We’re running into the same issue with EKS ---
**Author:** ![mayana\_s\_khan](https://avatars.discourse-cdn.com/v4/letter/m/f1d935/32.png) [@mayana\_s\_khan](https://community.dynatrace.com/u/mayana_s_khan)\ **Post date:** [October 15, 2019, 8:01am UTC](https://community.dynatrace.com/t/connectivity-problem-kube-proxy-and-oneagent/22130/3 "2019-10-15T08:01:06Z")
Hi, 443 and 8443 ports are opened between k8s containers and CAG/EAG servers? Download the support archive and check for erros in logs. Host--\>Process and Container(select the process which Activation of deep monitoring was unsuccessful) --\>click on the 3 dots and download support achieve. check the logs for errors. Regards, Mayana Khan ---
**Author:** ![israel\_chavez](https://avatars.discourse-cdn.com/v4/letter/i/59ef9b/32.png) [@israel\_chavez](https://community.dynatrace.com/u/israel_chavez)\ **Post date:** [November 27, 2019, 9:05pm UTC](https://community.dynatrace.com/t/connectivity-problem-kube-proxy-and-oneagent/22130/4 "2019-11-27T21:05:28Z")
hello, anyone found the answer for this? ---
**Author:** ![MaciejNeumann](https://avatars.discourse-cdn.com/v4/letter/m/5e9695/32.png) [@MaciejNeumann](https://community.dynatrace.com/u/MaciejNeumann)\ **Post date:** [December 19, 2022, 12:53pm UTC](https://community.dynatrace.com/t/connectivity-problem-kube-proxy-and-oneagent/22130/5 "2022-12-19T12:53:45Z")
Hello everyone, There is now an article in Dynatrace documentation about troubleshooting issues on Kubernetes, including connectivity issues. You can check it out here: [Connectivity issues between Dynatrace and your cluster](https://www.dynatrace.com/support/help/shortlink/kubernetes-troubleshoot#connect)