# Apply  new Dynakube oneAgent parameters, can  the operator change the oneAgent monitoring mode (infra/fullstack)

**URL:** <https://community.dynatrace.com/t/apply-new-dynakube-oneagent-parameters-can-the-operator-change-the-oneagent-monitoring-mode-infra-fullstack/55157>\
**Category:** Container platforms\
**Tags:** openshift, dynatrace-operator, kubernetes\
**Created:** [March 2, 2026, 3:33pm UTC](https://community.dynatrace.com/t/apply-new-dynakube-oneagent-parameters-can-the-operator-change-the-oneagent-monitoring-mode-infra-fullstack/55157 "2026-03-02T15:33:58Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![henk\_stobbe](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/henk_stobbe/32/30434_2.png) [@henk\_stobbe](https://community.dynatrace.com/u/henk_stobbe)\
**Post date:** [March 2, 2026, 3:33pm UTC](https://community.dynatrace.com/t/apply-new-dynakube-oneagent-parameters-can-the-operator-change-the-oneagent-monitoring-mode-infra-fullstack/55157/1 "2026-03-02T15:33:58Z")

</div>

Hello,

I&nbsp; modified the

## `.spec.oneAgent.cloudNativeFullStack  to `

## `.spec.oneAgent.hostMonitoring`

I was expecting the oneAgent to be set to infra by the operator (from full stack)

Am I expecting to much )-;

KR Henk

---

<div class="post-metadata">

**Author:** ![t\_pawlak](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/t_pawlak/32/14991_2.png) [@t\_pawlak](https://community.dynatrace.com/u/t_pawlak)\
**Post date:** [March 14, 2026, 8:58pm UTC](https://community.dynatrace.com/t/apply-new-dynakube-oneagent-parameters-can-the-operator-change-the-oneagent-monitoring-mode-infra-fullstack/55157/2 "2026-03-14T20:58:47Z")

</div>

Hi Henk,  
not really, but the expectation needs one extra step. When you change from .spec.oneAgent.cloudNativeFullStack to .spec.oneAgent.hostMonitoring, the Operator updates the monitoring mode, but pods that were already injected in cloud-native full-stack mode are not converted in place. According to Dynatrace docs, when switching from applicationMonitoring or cloudNativeFullstack to hostMonitoring, the previously instrumented pods need to be restarted. After that, you should see infra/host-monitoring-only behavior.

---

<div class="post-metadata">

**Author:** ![sujit\_k\_singh](https://avatars.discourse-cdn.com/v4/letter/s/34f0e0/32.png) [@sujit\_k\_singh](https://community.dynatrace.com/u/sujit_k_singh)\
**Post date:** [March 16, 2026, 5:51am UTC](https://community.dynatrace.com/t/apply-new-dynakube-oneagent-parameters-can-the-operator-change-the-oneagent-monitoring-mode-infra-fullstack/55157/3 "2026-03-16T05:51:50Z")

</div>

Hello&nbsp;[@t\_pawlak](https://community.dynatrace.com/user/42367)

Nice explanation 👍  
The key takeaway is that changing the DynaKube updates the mode for new pods, but already injected pods must be restarted to actually drop full‑stack injection and behave as host‑only — that detail is easy to miss.&nbsp;:blush: