Explore >> Select a destination
|
You are here 
|
rudimartinsen.com | ||
| | | | |
www.awelm.com
|
|
| | | | | At OpenAI I have spent the last few months of my life developing a Kubernetes scheduler plugin to customize preemption to better suit our ML workloads. | |
| | | | |
jreypo.io
|
|
| | | | | The easiest way to have a Kubernetes cluster up and running in Azure in a short amount of time is by using AKS service, also if you want a more granular control of your cluster or a more customized cluster you can alway use AKS-Egine. | |
| | | | |
blog.nodraak.fr
|
|
| | | | | TL;DR: There is no best architecture, it all depends on your requirements and resources Clusters with 1 to 3 nodes are good for testing, but for production you should have at least 5 nodes Feel free to do differently as I say Introduction Since its launch in 2015, Kubernetes is the new bitcoin and every company wants to migrate all its infrastructure (which is obviously made of hundreds of microservices) to show how cool they are. | |
| | | | |
arveknudsen.com
|
|
| | | In my previous blog post I showed how to use the Kops tool to create a production ready Kubernetes cluster on Amazon Web Services (AWS). In this follow-up post I will show how to install Elasticsearch and its graphical counterpart Kibana in the cluster, in order to be able to collect and store logs from your cluster and search/read them. We will also install Fluentd as this component is responsible for transmitting the standard Kubernetes logs to Elasticsearch. | ||
