# Dynatrace operator auto update

**URL:** <https://community.dynatrace.com/t/dynatrace-operator-auto-update/38765>\
**Category:** Container platforms\
**Tags:** updates, dynatrace-operator\
**Created:** [March 9, 2023, 2:48pm UTC](https://community.dynatrace.com/t/dynatrace-operator-auto-update/38765 "2023-03-09T14:48:38Z")\
**Posts on this page:** 6\
**Page:** 1

<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:** [March 9, 2023, 2:48pm UTC](https://community.dynatrace.com/t/dynatrace-operator-auto-update/38765/1 "2023-03-09T14:48:38Z")

</div>

Hi Folks,

As far as I remember dynatrace operator auto update did not work perviously. We always upgraded manually the operator time to time.&nbsp; Today we observed that 0.10.02 upgraded to 0.10.03. It a good news we can forget the manual update.

Did I missed something or the auto update worked before? But since when?

I have not found any useful infromation in the documnetation and on the dynatrace operator git hub.

 ![Mizs_0-1678372880642.png](https://global.discourse-cdn.com/dynatrace/original/2X/9/95ae3635242f2f05ed88a61411bc1fda45850b95.png)

Bring me into the light.

Thanks in advance.

Best regards,

Mizső

---

<div class="post-metadata">

**Author:** ![Romanenkov\_Al3x](https://dub1.discourse-cdn.com/dynatrace/user_avatar/community.dynatrace.com/romanenkov_al3x/32/36257_2.png) [@Romanenkov\_Al3x](https://community.dynatrace.com/u/Romanenkov_Al3x)\
**Post date:** [March 11, 2023, 9:53pm UTC](https://community.dynatrace.com/t/dynatrace-operator-auto-update/38765/2 "2023-03-11T21:53:25Z")

</div>

Bye Bye manual updates&nbsp;😃

Awesome. I will go to test it by myself.

---

<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:** [March 13, 2023, 7:34am UTC](https://community.dynatrace.com/t/dynatrace-operator-auto-update/38765/3 "2023-03-13T07:34:22Z")

</div>

Looks like the update is done by the platform (OpenShift in your screenshot?) and not by the operator itself - so it’s pretty dependent on how you deploy the operator, isn’t it?

---

<div class="post-metadata">

**Author:** ![shahinm](https://avatars.discourse-cdn.com/v4/letter/s/7ab992/32.png) [@shahinm](https://community.dynatrace.com/u/shahinm)\
**Post date:** [March 13, 2023, 9:05am UTC](https://community.dynatrace.com/t/dynatrace-operator-auto-update/38765/4 "2023-03-13T09:05:04Z")

</div>

Hello,

There was an improvement within the OLM Marketplace listing (not visible in the Dynatrace Operator’s GitHub repo), which caused the operator trigger an auto-upgrade. Please note that the change is only valid for the operator installed via the OCP operator hub.

---

<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:** [March 13, 2023, 9:14am UTC](https://community.dynatrace.com/t/dynatrace-operator-auto-update/38765/5 "2023-03-13T09:14:52Z")

</div>

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

In this case it was installed via the OCP operator hub. Thanks for the information.

Best regards,

Mizső

---

<div class="post-metadata">

**Author:** ![gouthamt](https://avatars.discourse-cdn.com/v4/letter/g/b5a626/32.png) [@gouthamt](https://community.dynatrace.com/u/gouthamt)\
**Post date:** [May 24, 2023, 8:04pm UTC](https://community.dynatrace.com/t/dynatrace-operator-auto-update/38765/6 "2023-05-24T20:04:44Z")

</div>

Hi Shahinm,

Is a way to disable this trigger for auto-upgrade.

Thanks