Re:Kubernetes 1.11 includes In-Cluster Service Load Balancin...
by jacques_chester on Thursday June 28, 2018 @07:38AM
(#17415997)
> K8S is only supported on expensive hosts (AWS, GCE, Azure), is it possible to spin it up on hetzner/ovh or another provider that is cheaper than AWS, possibly even on my own hardware?
Of course. There are literally dozens of distributions and repackaged versions now[0]. The advantage of GKE et al is that they keep them up to date -- still a bit harder than it looks.
> Be cheap
It very much depends on what "cheap" means and what your needs are. GKE with a cluster autoscaler is fairly inexpensive for what you get. But if your time is free and you like to tinker, self-managing on a VPS might be for you.
Be prepared to invest a fair amount of time. Kubernetes is simple in each part, but there are lots of parts to learn.
> Automatic failover (This should cover majority of downtime imho)
This is more of an app concern. Kubernetes itself won't really do this for you. Something like Istio will probably also be necessary to help with traffic management.
> Backups
Very much up to the distribution / hosting environment.
> Automatic scalability (CPU over 95% for last 2 minutes or smth like that? add new containers pls)
Horizontal Pod Autoscaler; a Vertical Pod Autoscaler is under development. Other autoscalers are being developed for more specialised uses (I've worked on one) and I expect there will be some concept of pluggable autoscaling soon.
> Load balancing
Numerous solutions in this area. Typically left to the IaaS. Istio can do this.
> How are K8S backups handled? ... several containers spawned of the DB
Regarding DB backups: I would again use a hosted service if at all possible. Several containers can share a volume in a Pod or across Pods. But long-running stateful services is not yet quite the Kubernetes sweet spot.
> What restarts K8S orchestrator if it fails?
Again, numerous solutions. I work for Pivotal, our solution in PKS is to run everything with BOSH. Something like GKE uses Google's own monitoring and recovery systems.
I should add here that I don't think GKE is necessarily the "best" of the public hosted options. Just the only one I've used in anger so far. I actually prefer to do development work on minikube whenever I can. If you go down that route, shop around!
Of course. There are literally dozens of distributions and repackaged versions now[0]. The advantage of GKE et al is that they keep them up to date -- still a bit harder than it looks.
> Be cheap
It very much depends on what "cheap" means and what your needs are. GKE with a cluster autoscaler is fairly inexpensive for what you get. But if your time is free and you like to tinker, self-managing on a VPS might be for you.
Be prepared to invest a fair amount of time. Kubernetes is simple in each part, but there are lots of parts to learn.
> Automatic failover (This should cover majority of downtime imho)
This is more of an app concern. Kubernetes itself won't really do this for you. Something like Istio will probably also be necessary to help with traffic management.
> Backups
Very much up to the distribution / hosting environment.
> Automatic scalability (CPU over 95% for last 2 minutes or smth like that? add new containers pls)
Horizontal Pod Autoscaler; a Vertical Pod Autoscaler is under development. Other autoscalers are being developed for more specialised uses (I've worked on one) and I expect there will be some concept of pluggable autoscaling soon.
> Load balancing
Numerous solutions in this area. Typically left to the IaaS. Istio can do this.
> How are K8S backups handled? ... several containers spawned of the DB
Regarding DB backups: I would again use a hosted service if at all possible. Several containers can share a volume in a Pod or across Pods. But long-running stateful services is not yet quite the Kubernetes sweet spot.
> What restarts K8S orchestrator if it fails?
Again, numerous solutions. I work for Pivotal, our solution in PKS is to run everything with BOSH. Something like GKE uses Google's own monitoring and recovery systems.
I should add here that I don't think GKE is necessarily the "best" of the public hosted options. Just the only one I've used in anger so far. I actually prefer to do development work on minikube whenever I can. If you go down that route, shop around!
[0] https://kubernetes.io/partners/