# AWX 19.x operator based on Helm 3 Manifest from AWX 17.x

**URL:** <https://forum.ansible.com/t/awx-19-x-operator-based-on-helm-3-manifest-from-awx-17-x/35753>\
**Category:** AWX Project\
**Tags:** awx\
**Created:** [September 17, 2021, 7:08am UTC](https://forum.ansible.com/t/awx-19-x-operator-based-on-helm-3-manifest-from-awx-17-x/35753 "2021-09-17T07:08:43Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![Nik\_Tetteh-Lartey](https://avatars.discourse-cdn.com/v4/letter/n/9e8a1a/32.png) [@Nik\_Tetteh-Lartey](https://forum.ansible.com/u/Nik_Tetteh-Lartey)\
**Post date:** [September 17, 2021, 7:08am UTC](https://forum.ansible.com/t/awx-19-x-operator-based-on-helm-3-manifest-from-awx-17-x/35753/1 "2021-09-17T07:08:43Z")

</div>

Hi Team,

I’m thinking how to upgrade from AWX 17.x to AWX 19.x.

I have my AWX 17.x deployments based on a Helm 3 Chart. So getting a AWX 19.x operator to deploy AWX with my particular customisations, I thought I could just use the latest 19.x operator with a Helm manifest dump from specific AWX 17.x deployments. I have not even tried this yet, but it seems viable from my novice point of view of this operator.

Can experts from this group confirm/refute my assertions on the viability of this approach please?