Rolling your own servers with Kubernetes
gravitational.com
Rolling your own servers with Kubernetes
1–10 of 209 posts
Re: Rolling your own servers with Kubernetes
#2I used to specialize in 2 - 10 rack build outs, but its been nearly a decade since those gigs evaporated. I wonder if k8s creates a new niche for it.
Re: Rolling your own servers with Kubernetes
#3So what is Gravity? kops/kubespray without an MIT license?
Re: Rolling your own servers with Kubernetes
#4You can colo your server and roll your own k8s clusters. But you can't afford the luxury of high throughput networking, EBS, etc., and don't forget HA options (Multi-AZ) for your clusters.
Re: Rolling your own servers with Kubernetes
#5The next-to-last line cracked me up: "The costs can be much lower… or much higher!"
Re: Rolling your own servers with Kubernetes
#6I am curious to see how they recommend handling storage on bare metal k8s.
Re: Rolling your own servers with Kubernetes
#7Last physical datacenter my team at the time ran our app in we spent weeks troubleshooting some hardware network driver issues that caused the network to drop. Was an enormous distraction and Dell and VMware support were useless at resolving it for us. I’m glad to have others deal with those low level “oh it must just be your setup” issues.
Re: Rolling your own servers with Kubernetes
#8Last physical datacenter my team at the time ran our app in we spent weeks troubleshooting some hardware network driver issues that caused the network to drop. Was an enormous distraction and Dell and VMware support were useless at resolving it for us. I’m glad to have others deal with those low level “oh it must just be your setup” issues.
At the scale where owning infrastructure makes sense, that's not a distraction but some team's full-time mission.
Re: Rolling your own servers with Kubernetes
#9I am curious to see how they recommend handling storage on bare metal k8s.
In many environments, you don't actually need distributed storage:
- Application servers are stateless.
- All state lives in stateful databases.
- Those database handle high availability at the application layer by replication data, so you can use local storage and deploy them using StatefulSets. Has the extra benefit of avoiding the network storage latency penalty.
Re: Rolling your own servers with Kubernetes
#10Last physical datacenter my team at the time ran our app in we spent weeks troubleshooting some hardware network driver issues that caused the network to drop. Was an enormous distraction and Dell and VMware support were useless at resolving it for us. I’m glad to have others deal with those low level “oh it must just be your setup” issues.
Until you hit this can not happen we will not spend time looking into it issue in a cloud :)