# OpenShift - ActiveGate usage

**URL:** <https://community.dynatrace.com/t/openshift-activegate-usage/39741>\
**Category:** Container platforms\
**Tags:** openshift, kubernetes\
**Created:** [May 15, 2023, 9:59am UTC](https://community.dynatrace.com/t/openshift-activegate-usage/39741 "2023-05-15T09:59:59Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![Malaik](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/malaik/32/32673_2.png) [@Malaik](https://community.dynatrace.com/u/Malaik)\
**Post date:** [May 15, 2023, 9:59am UTC](https://community.dynatrace.com/t/openshift-activegate-usage/39741/1 "2023-05-15T09:59:59Z")

</div>

Dear Community,

I have a question regarding OpenShift and AG usage:

As per the below screenshot, my OpenShift servers are using the internal AG on Kubernetes, what is the conclusion that we can find here:

OneAgent is communicating to Kubernetes AG, and that AG forward to Dynatrace env AG, that’s why we can find both on the properties of each agent?

 ![Malaik_0-1684144528339.png](https://global.discourse-cdn.com/dynatrace/original/2X/1/1c369d94632dcf26e84223d32c97f3b4acfb02b0.png)

---

<div class="post-metadata">

**Author:** ![mizso74](https://avatars.discourse-cdn.com/v4/letter/m/f05b48/32.png) [@mizso74](https://community.dynatrace.com/u/mizso74)\
**Post date:** [May 15, 2023, 11:50am UTC](https://community.dynatrace.com/t/openshift-activegate-usage/39741/2 "2023-05-15T11:50:27Z")

</div>

Hi&nbsp;[@Malaik](https://community.dynatrace.com/user/23195),

As far as I know the contenarized AG communicate directly with your managed host without ENV AG.

Best regards,

Mizső

---

<div class="post-metadata">

**Author:** ![Julius\_Loman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/julius_loman/32/51_2.png) [@Julius\_Loman](https://community.dynatrace.com/u/Julius_Loman)\
**Post date:** [May 15, 2023, 11:58am UTC](https://community.dynatrace.com/t/openshift-activegate-usage/39741/3 "2023-05-15T11:58:21Z")

</div>

Your situation is&nbsp;due to (some) code modules in applications running on those hosts communicating using the non-containerized active gate.

---

<div class="post-metadata">

**Author:** ![Malaik](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/malaik/32/32673_2.png) [@Malaik](https://community.dynatrace.com/u/Malaik)\
**Post date:** [May 15, 2023, 12:06pm UTC](https://community.dynatrace.com/t/openshift-activegate-usage/39741/4 "2023-05-15T12:06:02Z")

</div>

Thanks&nbsp;[@Julius\_Loman](https://community.dynatrace.com/user/3364)

How can we verify and change the things.

---

<div class="post-metadata">

**Author:** ![Julius\_Loman](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/julius_loman/32/51_2.png) [@Julius\_Loman](https://community.dynatrace.com/u/Julius_Loman)\
**Post date:** [May 15, 2023, 1:59pm UTC](https://community.dynatrace.com/t/openshift-activegate-usage/39741/5 "2023-05-15T13:59:38Z")

</div>

Downloading the support archive is probably the easiest method to verify the assumption and verify the logs of code modules. This also depends on DynaKube deployment options you have.

You can also reach out to DTONE who have access to DebugUI and help to identify the processes and reasons why the code modules are not connected to containerized ActiveGate.

---

<div class="post-metadata">

**Author:** ![dannemca](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/dannemca/32/7215_2.png) [@dannemca](https://community.dynatrace.com/u/dannemca)\
**Post date:** [May 15, 2023, 5:21pm UTC](https://community.dynatrace.com/t/openshift-activegate-usage/39741/6 "2023-05-15T17:21:42Z")

</div>

Did you set up any networkzone when configuring the dynakube? I do recommend to.

---

<div class="post-metadata">

**Author:** ![dannemca](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/dannemca/32/7215_2.png) [@dannemca](https://community.dynatrace.com/u/dannemca)\
**Post date:** [May 15, 2023, 5:22pm UTC](https://community.dynatrace.com/t/openshift-activegate-usage/39741/7 "2023-05-15T17:22:26Z")

</div>

hmm, just now I saw your screenshot and NZ is there… this is odd.

---

<div class="post-metadata">

**Author:** ![jsolerso1](https://avatars.discourse-cdn.com/v4/letter/j/eb9ed0/32.png) [@jsolerso1](https://community.dynatrace.com/u/jsolerso1)\
**Post date:** [October 31, 2023, 2:29pm UTC](https://community.dynatrace.com/t/openshift-activegate-usage/39741/8 "2023-10-31T14:29:22Z")

</div>

I don’t know if is the same problem. If in your environment you have a proxy defined to comunicate to the external dynatrace, in the kubeconfig yo have not to define a general proxy to allow the nodeagents to communicate to the internal activegate. To allow you internal activeGate to comunicate to the external dynatrace activeGates trough the proxy you have to add in kubeconfig AG definition section

```auto
<span class=""> <span class="">customProperties:</span></span>
<span class=""> <span class="">value:</span> <span class="">|</span></span>
<span class=""><span class=""> [http.client]</span></span>
<span class=""><span class=""> proxy-server=<your proxy></span></span>
<span class=""><span class=""> proxy-port=8080</span></span>
<span class=""><span class=""> proxy-non-proxy-hosts=*.xxx.xxx<br><br></span></span>I think is a workarround until the internal ActiveGate get the proper configuration from the dynatrace configuration to send the metrics to a internal AG

```