Highly available Kubernetes with batteries for small business
1–10 of 69 posts
Re: Highly available Kubernetes with batteries for small business
#2> This setup is not trully highly available. The whole cluster depends on the Synology as data storage. You could improve this further by replacing the centralized NAS with a distributed solution. But besides that the cluster is very solid and scalable
I understand that my local harddrive with excel spreadsheets detailing my entire business along side critical software is not the best place to store the lifeblood of my company, but throwing in the complexity of k8s in there and STILL not addressing the problem seems to be completely besides the point.
Digital Ocean managed k8s starts at $30 a month. Use that if you really want to pile on more stress running a company.
Re: Highly available Kubernetes with batteries for small business
#3> This setup is not trully highly available. The whole cluster depends on the Synology as data storage. You could improve this further by replacing the centralized NAS with a distributed solution. But besides that the cluster is very solid and scalable I understand that my local harddrive with excel spreadsheets detailing my entire business along side critical software is not the best place to store the lifeblood of…
GKE can be under that for a single node, a real setup starts at a few hundred dollars no matter where you are.
I find it amusing I spend more on Kates than cars
Re: Highly available Kubernetes with batteries for small business
#4> Kindie (Kubernetes Individual) is an opinionated Kubernetes cluster setup for individuals or small business.
I do think small business and individual shouldn't use kubernetes because it's too much overhead. Even if it's managed in a public cloud. It has too many issues with too little benefits. It's simply not worth it.
Of course if writing YAML files in YAML and golang templates, or having to deal with network errors for no reason is your thing, go for it.
Re: Highly available Kubernetes with batteries for small business
#5It feels like a huge hassle for a small business. Use a cloud, it's not that expensive. If, not even using a cloud is an option, you can still mount NFS, use a bridged network and use DHCP from that router, and run your software in systemd/upstart or simple Docker containers.
I don't like to sound like a grumpy old man that yells at new tech, I'm all good for experimentation home setups involving these, but every component you add is another thing to manage and monitor, even if you are a small business, you are still a business that you can spend your time on better things and sleep better at night.
Re: Highly available Kubernetes with batteries for small business
#6> Kindie (Kubernetes Individual) is an opinionated Kubernetes cluster setup for individuals or small business. I do think small business and individual shouldn't use kubernetes because it's too much overhead. Even if it's managed in a public cloud. It has too many issues with too little benefits. It's simply not worth it. Of course if writing YAML files in YAML and golang templates, or having to deal with network err…
My experience using GKE so far has been fairly good - it's not that much more difficult than using Google App Engine, and we're not locked into a single provider.
Re: Highly available Kubernetes with batteries for small business
#7small businesses should use SaaS
Re: Highly available Kubernetes with batteries for small business
#8> This setup is not trully highly available. The whole cluster depends on the Synology as data storage. You could improve this further by replacing the centralized NAS with a distributed solution. But besides that the cluster is very solid and scalable I understand that my local harddrive with excel spreadsheets detailing my entire business along side critical software is not the best place to store the lifeblood of…
exactly, this makes absolutely no sense for a small business. Managed DO / GKE is a much better idea, maintaining K8's is the last thing a small business should focus on.
Re: Highly available Kubernetes with batteries for small business
#9It feels like a huge hassle for a small business. Use a cloud, it's not that expensive. If, not even using a cloud is an option, you can still mount NFS, use a bridged network and use DHCP from that router, and run your software in systemd/upstart or simple Docker containers. I don't like to sound like a grumpy old man that yells at new tech, I'm all good for experimentation home setups involving these, but every com…
[deleted]
Re: Highly available Kubernetes with batteries for small business
#10Hello, just out of curiosity, is using the NFS Client Provisioner Helm chart necessary anymore for normal kubernetes deployments? My company was using it, but it became a bit of a hassle on GKE for our team, as we found that A) if you tried to reprovision the NFS Client Provisioner then it would no longer mount the NFS share directly, it would create a new subdirectory and the files in the top level of the NFS share would be inaccessible within our pods, and B) It did not support NFSv4. After some research we found that Kubernetes is able to utilize NFS shares natively these days. You can either mount a NFS share directly in a pod as long as its reachable in the network:
https://docs.docker.com/ee/ucp/kubernetes/storage/use-nfs-vo...
However, if you still would like to pre-provision the NFS share as a PV/PVC you are also able to do that and expose the NFS mount as a Kubernetes Object.
https://docs.docker.com/ee/ucp/kubernetes/storage/use-nfs-vo...
Just wondering, now that NFS mounts are directly available within Kubernetes, is there any advantages to utilizing a "3rd party" NFS Client Provisioner Helm deployment?
Anyways, looks like a really great write up. Although Kubernetes can be a big hassle for small teams, I feel like its slowly becoming more and more user accessible and user friendly to more organizations. Even with the mental overhead and hassle of running kubernetes, my team at work has seen some clear benefits from going to an ec2/ansible based architecture to a GKE/helm based architecture.