# Kubernetes offline, deployment issues with EKS

**URL:** <https://community.dynatrace.com/t/kubernetes-offline-deployment-issues-with-eks/47794>\
**Category:** Container platforms\
**Tags:** aws, activegate, kubernetes\
**Created:** [September 18, 2024, 4:57pm UTC](https://community.dynatrace.com/t/kubernetes-offline-deployment-issues-with-eks/47794 "2024-09-18T16:57:13Z")\
**Posts on this page:** 4\
**Page:** 1

<div class="post-metadata">

**Author:** ![Lamiaa](https://avatars.discourse-cdn.com/v4/letter/l/d07c76/32.png) [@Lamiaa](https://community.dynatrace.com/u/Lamiaa)\
**Post date:** [September 18, 2024, 4:57pm UTC](https://community.dynatrace.com/t/kubernetes-offline-deployment-issues-with-eks/47794/1 "2024-09-18T16:57:13Z")

</div>

We have an EKS component in aws that is private, so we created an AG environment to be the proxy between the EKS and the saas environment. We opeted for a offline deployment by pulling and pushing the images and we had the pods all running (we used the apiurl of the activegate in dynakube.yaml “apiUrl: https://\<activegate-host\>:9999/e/\<environment-id\>/api”) and the cluster kub shows up in the Dynatrace UI. But after a 15 min, dynakube AG (containerized AG) goes offline in the Dynatrace UI without its pod being down and the monitoring goes down also, but the dynakube oneagents still online.

with that being said, the cluster can communicate with the external ActiveGate in 9999 and the externel ActiveGate can reach the cluster Dynatrace SaaS.

any body can relate to this issue,

thank you for your time,

regards

---

<div class="post-metadata">

**Author:** ![p\_devulapalli](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/p_devulapalli/32/41590_2.png) [@p\_devulapalli](https://community.dynatrace.com/u/p_devulapalli)\
**Post date:** [September 19, 2024, 12:37am UTC](https://community.dynatrace.com/t/kubernetes-offline-deployment-issues-with-eks/47794/2 "2024-09-19T00:37:43Z")

</div>

Hi&nbsp;[@Lamiaa](https://community.dynatrace.com/user/80881)

Have you tried looking into the AG logs to see if you can find something ?

```markup
kubectl logs dynakube-activegate-0 -n dynatrace

```

Below command also provides some info for troubleshooting

```markup
kubectl exec deploy/dynatrace-operator -n dynatrace -- dynatrace-operator troubleshoot

```

---

<div class="post-metadata">

**Author:** ![Fin\_Ubels](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/fin_ubels/32/18008_2.png) [@Fin\_Ubels](https://community.dynatrace.com/u/Fin_Ubels)\
**Post date:** [September 19, 2024, 1:26am UTC](https://community.dynatrace.com/t/kubernetes-offline-deployment-issues-with-eks/47794/3 "2024-09-19T01:26:20Z")

</div>

Hey Lamiaa, you could also try looking into some self monitoring metrics for activegates. Such as&nbsp;dsfm:active\_gate.kubernetes.api.query\_count:splitBy(status\_code,status\_reason,path) which will show failing K8s requests. There are some other useful dimensions as well. Can be a good place to start.

---

<div class="post-metadata">

**Author:** ![PacoPorro](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/pacoporro/32/36087_2.png) [@PacoPorro](https://community.dynatrace.com/u/PacoPorro)\
**Post date:** [September 19, 2024, 6:50am UTC](https://community.dynatrace.com/t/kubernetes-offline-deployment-issues-with-eks/47794/4 "2024-09-19T06:50:08Z")

</div>

Hi&nbsp;  
The containerized AG should be able to connect to the cluster. There’s no chained AG communication.