I am trying to setup discourse for my organisation on k8s. However there are few issues I am facing. When I try to deploy the bootstrapped image on kubernetes it tries to do stuff like git pull pups and git pull discourse which doesnt work since I am on a private network without any access to the …

[صورة] Divyaanand_Sinha: When I try to deploy the bootstrapped image on kubernetes it tries to do stuff like git pull pups and git pull discourse which doesnt work Are you sure you are deploying an already bootstrapped image? Sounds like you pushed the wrong image to your registry.

Oh is it, I am using the image created by ./launcher bootstrap app So you are saying that the final bootstrapped image shouldn’t be having any such dependencies?

[صورة] Divyaanand_Sinha: So you are saying that the final bootstrapped image shouldn’t be having any such dependencies? No it won’t. After bootstrapping, there will be a local_discourse/app image. That is the one that you need to push to the registry and use elsewhere.

One final doubt, so it seems i was pushing the wrong image, my bad. So after i push the actual image I can change the env variables during k8s deployment right? Like DISCOURSE_DB_HOST etc? Because I have a separate postgres cluster and redis cluster!

[صورة] Divyaanand_Sinha: One final doubt, so it seems i was pushing the wrong image, my bad. Been there, done that. No worries, that is a very common mistake. That is why I asked :stuck_out_tongue: [صورة] Divyaanand_Sinha: So after i push the actual image I can change the env variables d…

So i already have an instance of discourse running but thats on bare metal, i want to move it to k8s, and connect to the same db the bare metal one was using.

Or if possible can I do the bootstrap again with the DISCOURSE_DB_HOST and DISCOURSE_DB_NAME pointing to the same db the bare metal one is using?

That should work! You may want to stop the current Discourse container that is connected to the DB while doing that, because migrations may make it behave in a broken way.

If I create a fresh new empty db and bootstrap using that, then is it possible for me to migrate the data from the UI instead (using the UI of the old discourse instance and the new discourse instance) like /admin/backups? I want to avoid corrupting the old DB , its being used by a lot of users.

نقاش حول k8s على شبكة خاصة

مطور

pfaffman (Jay Pfaffman) 3 يونيو 2020، 3:24م 11

You can’t migrate from the ux.

See Introducing Post Deployment Migration. This allows you to migrate the database such that it works for both the old and new container, then do final migrations after you deploy.

إعجاب واحد (1)

الموضوع		الردود	مرات العرض
Installing on Kubernetes Self-hosting unsupported-install	55	25047	6 فبراير 2026
Discourse setup on kubernetes cluster using HELM Self-hosting unsupported-install	3	3778	3 مارس 2023
Docker/Kubernetes: Location of launcher Support unsupported-install	10	1311	4 فبراير 2023
Unable to create web_only image for a fresh install Self-hosting two-container	10	870	25 فبراير 2021
Switching to another Redis instance? Self-hosting	5	1301	10 أكتوبر 2019

نقاش حول k8s على شبكة خاصة

الموضوعات ذات الصلة