# Try more k8s deployments

**URL:** <https://aiida.discourse.group/t/try-more-k8s-deployments/66>\
**Category:** Ideas\
**Created:** [August 17, 2023, 8:39am UTC](https://aiida.discourse.group/t/try-more-k8s-deployments/66 "2023-08-17T08:39:48Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![jusong.yu](https://yyz2.discourse-cdn.com/free1/user_avatar/aiida.discourse.group/jusong.yu/32/3_2.png) [@jusong.yu](https://aiida.discourse.group/u/jusong.yu)\
**Post date:** [August 17, 2023, 8:39am UTC](https://aiida.discourse.group/t/try-more-k8s-deployments/66/1 "2023-08-17T08:39:48Z")

</div>

We were using k8s to deploy AiiDAlab to [MarketPlace](https://github.com/aiidalab/aiidalab-docker-stack-demo) and using [microk8s recipe](https://github.com/aiidalab/aiidalab-microk8s-deploy) for internal THEOS/PSI deployments.  
We also have k8s recipes to do it. The k8s is the production way to have a robust deployment, so we need to bring it back and make it more generic in the future.  
Check this topic along with [A demo instance on Azure using the K8S recipes](https://aiida.discourse.group/t/a-demo-instance-on-azure-using-the-k8s-recipes/64/1) which share the common configurations.