No thanks, that’s quite expensive just to host some side projects. The basic setup with a container registry and a 2 node Kubernetes cluster will cost you 44$/month.
That’s true, but I didn’t consider the free tier since it is very limited. Just 1 repository and 500mb of storage, that’s maybe one to two large container(s).
There’s definite value in learning kubernetes,but the “reduces vendor lock-in” argument irritates me, because it really isn’t true. The second you move past just running a container, things start to differ:
This seems quite costly and quite a few steps. Sure you have a cluster but on side projects, I personally generally wouldn’t need that. For easy of deployment, I have a script that install docker/compose via ssh and so after that, I can deploy anything with ease using docker-compose. No need to install anything else manually and the setup is the same on my MacBook as on the vps. And that works on ~$1/mo VPS setups. These are side projects; they don’t need to be bulletproof (but so far they are; I am quite surprised about the uptime and quality of modern hosters).
Instead of paying for a registry service, I wonder whether it is a bad pattern to host an image registry within the cluster. I’ve done it a few times, but I’m not sure if it’s inappropriate for any specific reasons.
Is it really in people’s best interest to learn how to setup cloud environments by clicking around in web consoles/dashboards? Seems like a bad idea for anything more than a tutorial, or if you’re exploring something, maybe.
I don’t know, I caught the declarative infrastructure as code bug before terraform was even a thing, with puppet and vagrant, back in 2014-ish, and I have not looked back.
It’s really quite easy. I use the datacenter name “standalone” and put a consul instance and nomad instance on a box, then just put jobs on it. I use this for things like camera NVRs and “I need to run a few OCI containers, I guess”.
Small, easy, fully in automation. And I don’t need to mess with k8s which the vast majority of people don’t need because most people are not google. Also nomad is just nice :)
While I do enjoy reading a well written blog post I understand that it may not be worth the effort to you. I’m mostly curious about what the workflow itself looks like when you say you “need to run a few OCI containers”. This is coming from someone who isn’t experienced at all with Consul or Nomad, so maybe the thing for me would be to just read their documentation…
Thanks for yet another post! I noticed quite a few more typos this time around though, not sure if I’m the only one bothered by those:
“VSCode docker containers straight ro production”
“Learn Kubernetes alon the way”
“Make sure you chnage the registry accordingly”
There were also multiple instances of casing being off (e.g. “docker container” vs. “Docker container”, “yaml files” vs. “YAML files”, etc.). This isn’t to throw shade on you or anything, I truly appreciate your continued effort in authoring posts.
To anyone else getting started with K8S based tools like kubectl and helm I suggest taking a look at Hermit as it makes installing not only those tools but other ones as well dead simple. Here is a list of tools that can currently be installed. I’ve also submitted a PR to add doctl into the mix.
At work I’ve used Hermit to greatly simplify installing common tooling by removing the requirement that people go through various bits of documentation on various sites to just running, for example, hermit install gcloud helm kubectl kubectx kubens velero.
No thanks, that’s quite expensive just to host some side projects. The basic setup with a container registry and a 2 node Kubernetes cluster will cost you 44$/month.
You can start with as little as $12/mo – one node cluster, free tier registry.
That’s true, but I didn’t consider the free tier since it is very limited. Just 1 repository and 500mb of storage, that’s maybe one to two large container(s).
There’s definite value in learning kubernetes,but the “reduces vendor lock-in” argument irritates me, because it really isn’t true. The second you move past just running a container, things start to differ:
This seems quite costly and quite a few steps. Sure you have a cluster but on side projects, I personally generally wouldn’t need that. For easy of deployment, I have a script that install docker/compose via ssh and so after that, I can deploy anything with ease using docker-compose. No need to install anything else manually and the setup is the same on my MacBook as on the vps. And that works on ~$1/mo VPS setups. These are side projects; they don’t need to be bulletproof (but so far they are; I am quite surprised about the uptime and quality of modern hosters).
Instead of paying for a registry service, I wonder whether it is a bad pattern to host an image registry within the cluster. I’ve done it a few times, but I’m not sure if it’s inappropriate for any specific reasons.
Only if you don’t wanna manage it.
Is it really in people’s best interest to learn how to setup cloud environments by clicking around in web consoles/dashboards? Seems like a bad idea for anything more than a tutorial, or if you’re exploring something, maybe.
I don’t know, I caught the declarative infrastructure as code bug before terraform was even a thing, with puppet and vagrant, back in 2014-ish, and I have not looked back.
I have a simple nomad setup for side projects.
It’s really quite easy. I use the datacenter name “standalone” and put a consul instance and nomad instance on a box, then just put jobs on it. I use this for things like camera NVRs and “I need to run a few OCI containers, I guess”.
Small, easy, fully in automation. And I don’t need to mess with k8s which the vast majority of people don’t need because most people are not google. Also nomad is just nice :)
I would love to read a more detailed write-up about this setup. Do you have anything you can refer me to?
I’ve got saltstack config I can throw into a comment, I can stand up a blog, and I can be reached on IRC (oftc and libera). What suits your fancy?
Did you ever post this anywhere? Just curious about nomad :-) “Vaelatern” Vaelatern@lobste.rs writes:
While I do enjoy reading a well written blog post I understand that it may not be worth the effort to you. I’m mostly curious about what the workflow itself looks like when you say you “need to run a few OCI containers”. This is coming from someone who isn’t experienced at all with Consul or Nomad, so maybe the thing for me would be to just read their documentation…
Thanks for yet another post! I noticed quite a few more typos this time around though, not sure if I’m the only one bothered by those:
There were also multiple instances of casing being off (e.g. “docker container” vs. “Docker container”, “yaml files” vs. “YAML files”, etc.). This isn’t to throw shade on you or anything, I truly appreciate your continued effort in authoring posts.
To anyone else getting started with K8S based tools like
kubectlandhelmI suggest taking a look at Hermit as it makes installing not only those tools but other ones as well dead simple. Here is a list of tools that can currently be installed. I’ve also submitted a PR to adddoctlinto the mix.At work I’ve used Hermit to greatly simplify installing common tooling by removing the requirement that people go through various bits of documentation on various sites to just running, for example,
hermit install gcloud helm kubectl kubectx kubens velero.Thanks for the hints on the typos! I changed it!
hermitis a great tip; thank you!