# Migration from SAS to self-hosted kubernetes **URL:** \ **Category:** Self-hosting\ **Tags:** unsupported-install\ **Created:** [February 15, 2024, 12:01pm UTC](https://meta.discourse.org/t/migration-from-sas-to-self-hosted-kubernetes/295466 "2024-02-15T12:01:58Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![pfaffman](https://sea3.discourse-cdn.com/meta/user_avatar/meta.discourse.org/pfaffman/32/120154_2.png) [@pfaffman](https://meta.discourse.org/u/pfaffman)\ **Post date:** [February 15, 2024, 2:24pm UTC](https://meta.discourse.org/t/migration-from-sas-to-self-hosted-kubernetes/295466/3 "2024-02-15T14:24:11Z")
The bitnami image is probably on stable, so if you want to use it you’ll likely need to wait until the next stable release in 6-8 months. It’ll be lots easier to do a [standard install](https://meta.discourse.org/t/142537?silent=true), and unless you’ve got much more than a million page views/month, a single VM is probably Good Enough. If you do want k8s you can use launcher to build an image that you run with k8s. `./launcher start-cmd` will give you the settings you need to start the image. Changing the domain name isn’t a big deal, as if you do a restore it’ll remap everything. The bigger issue is to make sure that your backup includes the images and not links to them on the SAS S3 bucket. --- _[View the full topic](https://meta.discourse.org/t/migration-from-sas-to-self-hosted-kubernetes/295466)._