# Kubernetes Operator: feature.dynatrace.com/k8s-app-enabled not documented?

**URL:** <https://community.dynatrace.com/t/kubernetes-operator-feature-dynatrace-com-k8s-app-enabled-not-documented/55031>\
**Category:** Open Q&A\
**Tags:** documentation, infrastructure-operations\
**Created:** [February 18, 2026, 9:30am UTC](https://community.dynatrace.com/t/kubernetes-operator-feature-dynatrace-com-k8s-app-enabled-not-documented/55031 "2026-02-18T09:30:54Z")\
**Posts on this page:** 4\
**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:** [February 18, 2026, 9:30am UTC](https://community.dynatrace.com/t/kubernetes-operator-feature-dynatrace-com-k8s-app-enabled-not-documented/55031/1 "2026-02-18T09:30:54Z")

</div>

Hello,

This feature flag is still in generated yaml, but not to be found in the documentation…

[feature.dynatrace.com/k8s-app-enabled](http://feature.dynatrace.com/k8s-app-enabled)

 ![henk_stobbe_0-1771406958545.png](https://global.discourse-cdn.com/dynatrace/original/3X/e/0/e07f20fa2383c3187f32683faa6d7b63d1e3eb63.png)

All feature flags:

[https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/reference/dynakube-feature-flagshttps://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/deployment/application-observability](https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/reference/dynakube-feature-flags)

So what happened?

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:** [February 18, 2026, 9:50am UTC](https://community.dynatrace.com/t/kubernetes-operator-feature-dynatrace-com-k8s-app-enabled-not-documented/55031/2 "2026-02-18T09:50:52Z")

</div>

Hi,  
You’re not imagining it — [feature.dynatrace.com/k8s-app-enabled](http://feature.dynatrace.com/k8s-app-enabled) shows up in generated YAML snippets, but it’s not present in the official “DynaKube feature flags” reference list. That strongly suggests it’s a generator/wizard marker or an internal compatibility switch, not a public, supported feature flag.

IMO -&nbsp;It’s safe to remove it from your DynaKube YAML — if it’s not documented as a feature flag, you shouldn’t rely on it.

If this YAML came from the UI/wizard, treat it as a generated marker and consider filing it as a docs/generator inconsistency: examples include a flag that isn’t in the reference.

---

<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:** [February 18, 2026, 9:53am UTC](https://community.dynatrace.com/t/kubernetes-operator-feature-dynatrace-com-k8s-app-enabled-not-documented/55031/3 "2026-02-18T09:53:34Z")

</div>

Thanks for your swift and clear answer!😊

---

<div class="post-metadata">

**Author:** ![Enrico\_F](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/enrico_f/32/23774_2.png) [@Enrico\_F](https://community.dynatrace.com/u/Enrico_F)\
**Post date:** [July 9, 2026, 10:44am UTC](https://community.dynatrace.com/t/kubernetes-operator-feature-dynatrace-com-k8s-app-enabled-not-documented/55031/4 "2026-07-09T10:44:02Z")

</div>

6 months later and the flag is still part of the DynaKube samples on multiple doc pages e.g.

- [Get started with Kubernetes platform monitoring](https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/deployment/platform-observability)
- [Get started with Kubernetes platform monitoring + Application observability](https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/deployment/application-observability)
- [Get started with Kubernetes platform monitoring + Full-Stack observability](https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/deployment/full-stack-observability)

Has nobody reported this yet?

FWIW I just stumbled over this myself and left a UserSnap feedback on one of those pages.
