11–20 of 100 posts
Or... you could just install a Docker swarm in 10 minutes https://www.bretfisher.com/10-minutes-to-highly-available-do... No good reasons to use K8s outside multi-team enterprise stateful multi-tier architectures.
I think what type of k8s environment you use very much depends on what you're looking to get out of it. If it's experience deploying applications into containerized environments, then micro-k8s and k3s seem like reasonable choices, you don't really care about the setup of the underlying components, just that they present the k8s API. If you're looking for experience of managing k8s clusters, then either the distribut…
If we disregard one’s experience with Kubernetes as a factor, are there any other reasons you see to not use k8s at home?
Or... you could just install a Docker swarm in 10 minutes https://www.bretfisher.com/10-minutes-to-highly-available-do... No good reasons to use K8s outside multi-team enterprise stateful multi-tier architectures.
What I miss from all of these tutorials is one very important piece - how to handle network routing and dns automation within your home network, that's in typical scenario is being handled by the ingress/cloud controller. Without having automated (or easy enough) way of reaching the apps you're deploying there, each of these clusters is pretty much useless for users except for maybe learning basics of k8s, what's eas…
I use dynamic DNS with my Edgemax router. Something like inlets operator or cloudflare Argo are other options.
I think what type of k8s environment you use very much depends on what you're looking to get out of it. If it's experience deploying applications into containerized environments, then micro-k8s and k3s seem like reasonable choices, you don't really care about the setup of the underlying components, just that they present the k8s API. If you're looking for experience of managing k8s clusters, then either the distribut…
> if you're looking for something to run your home services long term, I would recommend not using Kubernetes If we disregard one’s experience with Kubernetes as a factor, are there any other reasons you see to not use k8s at home?
So outside of playing with Kubernetes for experience, why would you do that?
What I miss from all of these tutorials is one very important piece - how to handle network routing and dns automation within your home network, that's in typical scenario is being handled by the ingress/cloud controller. Without having automated (or easy enough) way of reaching the apps you're deploying there, each of these clusters is pretty much useless for users except for maybe learning basics of k8s, what's eas…
- specify a LAN IP for your ingress controller so it doesn't change.
- Use ddwrt/dnsmasq to point *.k8s.myhomenetwork.local to said IP
Once that's configured, you just configure the ingress hostname on services as you would "normally".
I think what type of k8s environment you use very much depends on what you're looking to get out of it. If it's experience deploying applications into containerized environments, then micro-k8s and k3s seem like reasonable choices, you don't really care about the setup of the underlying components, just that they present the k8s API. If you're looking for experience of managing k8s clusters, then either the distribut…
> if you're looking for something to run your home services long term, I would recommend not using Kubernetes If we disregard one’s experience with Kubernetes as a factor, are there any other reasons you see to not use k8s at home?
From a complexity perspective, you're adding more places for things to break. Instead of (say) running your apps in containers with Docker, you add pods, services and ingress as layers, which is more places for things to go wrong.
Earlier quoted context omitted.
I use dynamic DNS with my Edgemax router. Something like inlets operator or cloudflare Argo are other options.
I think the OP might be more asking about how to get local DNS automatically provisioned with the IP address of a service/container that has been deployed to the LAN.
Happy to see this. I think more orgs should be running more on-prem or colocated in a data center somewhere. Public clouds can be a rip off for larger projects