# Liquibase+k8s init container automation for new DDL and DML

**URL:** <https://forum.liquibase.org/t/liquibase-k8s-init-container-automation-for-new-ddl-and-dml/8482>\
**Category:** General Discussion\
**Created:** [August 1, 2023, 2:50am UTC](https://forum.liquibase.org/t/liquibase-k8s-init-container-automation-for-new-ddl-and-dml/8482 "2023-08-01T02:50:47Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jameswinnchester](https://avatars.discourse-cdn.com/v4/letter/j/838e76/32.png) [@jameswinnchester](https://forum.liquibase.org/u/jameswinnchester)\
**Post date:** [August 1, 2023, 2:50am UTC](https://forum.liquibase.org/t/liquibase-k8s-init-container-automation-for-new-ddl-and-dml/8482/1 "2023-08-01T02:50:47Z")

</div>

I’ve successfully created a local k8s cluster, deployed my apps, also using liquibase in init-container to run DDL and DML for my apps.  
My question is, every time I add a new DDL.xml or DML.xml in my app, do I have to manually create a new configmap to store the new DDL.xml and update deployment.yaml to recognize this new configmap?