# Ability to use annotations/labels for Kubernetes security context

**URL:** <https://community.dynatrace.com/t/ability-to-use-annotations-labels-for-kubernetes-security-context/48232>\
**Category:** Logs\
**Tags:** data-privacy-and-product-security, logs\
**Created:** [October 9, 2024, 1:03pm UTC](https://community.dynatrace.com/t/ability-to-use-annotations-labels-for-kubernetes-security-context/48232 "2024-10-09T13:03:51Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![ronmacdonald](https://avatars.discourse-cdn.com/v4/letter/r/a88e57/32.png) [@ronmacdonald](https://community.dynatrace.com/u/ronmacdonald)\
**Post date:** [October 9, 2024, 1:03pm UTC](https://community.dynatrace.com/t/ability-to-use-annotations-labels-for-kubernetes-security-context/48232/1 "2024-10-09T13:03:51Z")

</div>

It appears security context for log data only supports filters, not lookup or joins.&nbsp; I need to apply security context for logs by annotations/labels on the process group producing the logs.&nbsp; Is there a way to accomplish this currently?

---

<div class="post-metadata">

**Author:** ![ChadTurner](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/chadturner/32/161_2.png) [@ChadTurner](https://community.dynatrace.com/u/ChadTurner)\
**Post date:** [September 30, 2025, 7:05pm UTC](https://community.dynatrace.com/t/ability-to-use-annotations-labels-for-kubernetes-security-context/48232/2 "2025-09-30T19:05:47Z")

</div>

[@ronmacdonald](https://community.dynatrace.com/user/5224)&nbsp;were you able to get a solution to this? did you end up putting in a RFE? If so can you share it here?

---

<div class="post-metadata">

**Author:** ![ronmacdonald](https://avatars.discourse-cdn.com/v4/letter/r/a88e57/32.png) [@ronmacdonald](https://community.dynatrace.com/u/ronmacdonald)\
**Post date:** [September 30, 2025, 8:04pm UTC](https://community.dynatrace.com/t/ability-to-use-annotations-labels-for-kubernetes-security-context/48232/3 "2025-09-30T20:04:14Z")

</div>

This is a feature based based on supported OA, AG, and possibly the operator (we are cloud native).

The config is in the “cloud and virtualization \>\> Kubernetes telemetry enrichment”  
We are using k8 labels to set security\_context.&nbsp; We are seeing the value miss for some expected log records and are in early stages of investigating.