kubernetes VS Nomad

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

Also if you don’t want to look at kube then check out Nomad. https://www.nomadproject.io/

Hahaha sure: https://www.nomadproject.io it’s by HashiCorp.

Yeah, this pains me too. Here's a relevant issue to keep an eye on:

https://github.com/hashicorp/nomad/issues/3854

I've used an nginx-based S3 proxy in the past to get around this. Not ideal but it works.

At Lob, we currently use Convox as our deployment platform, a “roll your own Platform-as-a-Service” that you can install to handle container orchestration on AWS’s ECS (Elastic Container Service). Convox is showing its age and this year we began the process of replacing Convox with HashiCorp’s Nomad, a flexible workload orchestrator to deploy and manage our containers on AWS.

its an orchestration tool similar to something like K8S https://www.nomadproject.io/

That does seem better! Of course, there are a few lingering issues with support, but overall the trend is good: https://github.com/containers/podman/issues?q=is%3Aissue+is%...

Of course, there's no Swarm support, as evidenced by that very article:

> Caveats

> One known caveat is that Podman has not and will not implement the Swarm function. Therefore, if your Docker Compose instance uses Swarm, it will not work with Podman.

Feels like people will either be pigeonholed into Kubernetes for all of their deployments, or will have to migrate over to something like Hashicorp Nomad: https://www.nomadproject.io/

Curiously, it also supports Podman as a task driver: https://www.nomadproject.io/docs/drivers/podman

I'm not sure I understand the situation here, but for something like running one-off / batch jobs across nodes, that sounds like something nomad should cover, or maybe Ansible depending on what you need.