Skip to content
Discussion options

You must be logged in to vote

My successful migration looked like the following:

  1. Spin up a separate NC chart instance with the same values and a different name. I used <name>-ng.
  2. Change the persistence values to the desired ones.
  3. Change the application container deployment to 0 replicas.
  4. Copy the data folder in the old volume to the new data volume.
  5. Copy the config folder in the old volume to the new config volume.
  6. Copy the old database to the new database instance or change the config in the new chart instance
  7. Change the application container deployment to 1 replica again.

Pray you forgot nothing, and check the logs. I did this whole ordeal to see if it helps with container startup times, and sadly, it didn't help.

Replies: 1 comment

Comment options

You must be logged in to vote
0 replies
Answer selected by SchoolGuy
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Category
Q&A
Labels
None yet
1 participant