# Dynatrace Operator 1.8.1 upgrade related - java springboot pods crash-looping

**URL:** <https://community.dynatrace.com/t/dynatrace-operator-1-8-1-upgrade-related-java-springboot-pods-crash-looping/55858>\
**Category:** Container platforms\
**Tags:** dynatrace-operator, kubernetes\
**Created:** [May 10, 2026, 1:28am UTC](https://community.dynatrace.com/t/dynatrace-operator-1-8-1-upgrade-related-java-springboot-pods-crash-looping/55858 "2026-05-10T01:28:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![dyn98007](https://avatars.discourse-cdn.com/v4/letter/d/5daacb/32.png) [@dyn98007](https://community.dynatrace.com/u/dyn98007)\
**Post date:** [May 10, 2026, 1:28am UTC](https://community.dynatrace.com/t/dynatrace-operator-1-8-1-upgrade-related-java-springboot-pods-crash-looping/55858/1 "2026-05-10T01:28:40Z")

</div>

There was an upgrade of the DT Operator from version 1.6.3 (v1beta5) to 1.8.1(v1beta5).

After the deployment of 1.8.1 in the k8 cluster, The java springboot pods started crash-looping because the Dynatrace OneAgent isn’t injecting the enrichment properties file.

```auto
Error: java.io.FileNotFoundException: /var/lib/dynatrace/enrichment/endpoint/endpoint.properties (No such file or directory)

```

The failed Pod has an annotation:

- _[dynakube.dynatrace.com/reason:](http://dynakube.dynatrace.com/reason:) NoBootstrapperConfig_

The DT operator log has the below entry:

_$ kubectl logs -n dynatrace-system -l [app.kubernetes.io/name=dynatrace-operator](http://app.kubernetes.io/name=dynatrace-operator) --tail=200 | grep -E ‘bootstrapper|secret’ \> travel-bootstrapper.log_

_{“level”:“info”,“ts”:“2026-05-09T18:50:00.156Z”,“logger”:“pod-mutation-injection”,“msg”:“dynatrace-bootstrapper-certs is not available, trying to replicate”,“pod”:“keda-reflector-29639210-”}_  
_{“level”:“info”,“ts”:“2026-05-09T18:50:00.160Z”,“logger”:“pod-mutation-injection”,“msg”:“unable to copy source of integration-k8s-cluster-bootstrapper-certs as it is not available, injection not possible”,“pod”:“keda-reflector-29639210-”}_

In the impacted k8s cluster:

_$ kubectl get secrets -n dynatrace-system_

The output shows _bootstrapper-config_ cert , and NOT the _bootstrapper-certs_ .

The _-bootstrapper-certs_ secret was NOT generated.

Please advise

---

<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 10, 2026, 8:35pm UTC](https://community.dynatrace.com/t/dynatrace-operator-1-8-1-upgrade-related-java-springboot-pods-crash-looping/55858/2 "2026-05-10T20:35:35Z")

</div>

[@dyn98007](https://community.dynatrace.com/user/79860)&nbsp; The reason is described here&nbsp;[Troubleshooting — Dynatrace Docs](https://docs.dynatrace.com/docs/ingest-from/setup-on-k8s/deployment/troubleshooting#skipped-injection-reasons)&nbsp; (which you likely already know).

I recommend creating a support ticket at [https://support.dynatrace.com](https://support.dynatrace.com)&nbsp;as the reasons can vary.

---

<div class="post-metadata">

**Author:** ![dyn98007](https://avatars.discourse-cdn.com/v4/letter/d/5daacb/32.png) [@dyn98007](https://community.dynatrace.com/u/dyn98007)\
**Post date:** [November 5, 2026, 3:06am UTC](https://community.dynatrace.com/t/dynatrace-operator-1-8-1-upgrade-related-java-springboot-pods-crash-looping/55858/3 "2026-11-05T03:06:55Z")

</div>

> [@dyn98007](#):
>
> 1.6.3 (v1beta5) to 1.8.1(v1beta5).

The DT support recommendation was to migrate from 1.6.3 (v1beta5) to 1.7.3 , and then to 1.8.1
