kubernetes VS Packer

That error message seems to give much more results, such as: https://github.com/kubernetes/kubernetes/issues/36575

I mean and this is a weird idea, you could use Kubernetes and create a multi node cluster. the idea is that you would create a storage volume that is shared and sharded across all nodes in the cluster and then when one system fails, you can shift the traffic(using Ingress) to the other node where the container will then start to rebuild. It's a pretty complicated system but you can try that. You do need some basic concepts of server administration and configuration though.

Ali: Wow. Wait. Okay, so you really do everything. And something that was super interesting to me that you just said was that you studied and learned everything. You were building your own training plans and things like that. And I want to take this back to coding a little bit. And say you're talking to me here. You are literally talking to me. And right now, I'm trying to dive into Kubernetes. It's very overwhelming, and there's so much to it. So if you were in my shoes, how would you approach this problem? Because when you approach a new subject, new world, there are ways that you approach the problem to learn. So what does your approach generally look like?

The main site is at https://kubernetes.io. There's really good docs, which is sweet!

You know what, you are right. There isn't an "easy" way to do it. When I installed home assistant on my Pi, I actually just opted for a supervised instance running in Docker. Which IS supported. But is like, running home assistant on hard mode if you don't know how Docker works :) (waiting for it to come to Kubernetes for the real fun to begin.)

kubectl exec source code

https://www.packer.io/ https://docs.microsoft.com/en-us/azure/virtual-machines/linux/build-image-with-packer

Packer - https://www.packer.io/

I have faced this locking problem while trying to use packer for building out AMIs. It was a flaky process. I used to google it always and not figure out a solution and continue rerunning the builds for a long time.

But one of my colleagues figured out that it is probably because the apt-get is getting locked due to cloud-init and removed the flakiness by making packer wait[1] for cloud-init to complete before running the installation scripts that involved apt-get locking.

We too wished that there were more docs to help us, especially explaining how apt-get worked.

[1] https://github.com/hashicorp/packer/issues/2639#issuecomment...

You can create golden images with Hashicorp Packer.

And what I see day to day is Terraform, Chef. You also have things like Packer and Azure Image Builder, which is basically Packer, a lot of that. And then personally, just trying to wrap my head and wheels around Azure as a whole coming from an AWS background. I'm a firm believer in cloud is cloud is cloud, but also you have to know the difference between an S3 bucket and a Blob. The words are different, and the way things are structured are a little different so just understanding that coming from the AWS shop.

You could create such a thing with Packer I would think.

There's also Packer that can generate pre-built OS images. Rather than have dev machines be created and then immediately have to wait for changes to apply, you can pre-apply all the changes and boot them up directly.

For example, the cloud native way to apply updates is to not patch machines, but recycle all machines every X hours. Usually every 24 hours. They get all the latest patches from a pre-built and tested VM image. Images are typically pre-built by a provider, or customized with something like Packer.