# Rollback on Kubernetes when the update are done by jobs

**URL:** <https://forum.liquibase.org/t/rollback-on-kubernetes-when-the-update-are-done-by-jobs/9045>\
**Category:** General Discussion\
**Created:** [January 25, 2024, 9:57am UTC](https://forum.liquibase.org/t/rollback-on-kubernetes-when-the-update-are-done-by-jobs/9045 "2024-01-25T09:57:20Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![nathanboudart](https://avatars.discourse-cdn.com/v4/letter/n/54ee81/32.png) [@nathanboudart](https://forum.liquibase.org/u/nathanboudart)\
**Post date:** [January 25, 2024, 9:57am UTC](https://forum.liquibase.org/t/rollback-on-kubernetes-when-the-update-are-done-by-jobs/9045/1 "2024-01-25T09:57:20Z")

</div>

Hello,

We have a Kubernetes environment on witch we run Liquibase as a job, we create the script and update the changelog(in xml) with a new at the end of the changelog we compile a new image with the changes and run this image as a job. I would like to know in this situation how can I rollback a that did not produce the intended changes in database, as i can’t run the command (there is no instance of Liquibase)?

Thank you in advance for the support