Docker to Kubernetes Data Migration Made Easy!

[@DarrylGibbs]

I'm not on the K3s bus yet, but your videos make it seem so much more approachable than I would have thought. You're doing an amazing public service, good sir!

[@Jims-Garage]

Thanks, really appreciate your support

[@GeoffHalsey]

I'm blown away by the detail in this Kubernetes series. Amazing stuff!

[@Jims-Garage]

Thanks :) Although it's tanking my views on YT it has to be done, I don't see many people catering for it, and I feelcompelled to give you guys a working setup if I'm going to promote the use of Kubernetes in a homelab.

[@GeoffHalsey]

With the complexity of the subject and the hardware requirements (I have a Dell R620+Proxmox8), I can see why YT views maybe limited. Although not a novice, I must admit I'm reaching for my metaphorical 'stick on chest wig' to get through it🙂 It's easily most advance homelab project I've ever tried.

[@-rm-rf]

perfect follow up from last video!

[@Jims-Garage]

Thanks 👍

[@Silence1990]

Thank you ❤ Thats the Solution for my Reddit Post today

[@Jims-Garage]

Awesome, glad I could help you.

[@bababooey2329]

Thanks for the video. Also would be cool if you could touch the subject: migrating database content (tables and info all the info from it like postgres) from docker to kube. Also creating replicas with all the original content. (Heard people having problems with that)

[@Jims-Garage]

You should be able to migrate the database in the same way, or do an export with the database itself (which is usually always better). Replicas I would avoid with anything that needs persistence. Few homelab apps are designed for it.

[@vatsalyavigyaverma5494]

Thanks Jim as always, you cleared most of my storage doubt, but my website is js framework. yes nginx needed but I also have to build it. I think my options are gitops with custom image repository etc... Or remount again and rsync again. This time I will stick with kubernetes no more backing off.

[@BromZlab]

👌

[@crc-error-7968]

hello Jim and thanks 😉👍 I have a question ...I know is a little bit OT (as my usual 😇), but.. how can I keep updated the entire "infrastructure"? (I mean workers, master, admin and pods) On a vm with docker it is easy apt update/upgrade + docker compose pull/up -d. On this cluster can be done at the same way? update the single machines, and then use the kube command (or from GUI) to pull the new images? Could I have some sync problem during the update? Maybe because kubernates runs with different versions etc?

[@Jims-Garage]

Ubuntu cloud should auto update on rebooting, if not run the usual commands. You'll want to do this in series to allow the cluster to heal. This could also be automated by using something like ansible or jet porch. The pods can be updated by pulling the image or setting image pull policy to always.

[@crc-error-7968]

@@Jims-Garage thank you very much!