Source: thenewstack.io
A Deep Dive into Architecting a Kubernetes InfrastructureCategory: Software, Kubernetes, Infrastructure, Architecture, firewall, github, gitlab
This blog is a part of a series on Kubernetes and its ecosystem where we will dive deep into the infrastructure one piece at a time. So far in this series, we explored the various questions one might have when starting off with Kubernetes and its ecosystem and did our best to answer them.
In this blog, we will look at the best possible way to architect your infrastructure for your use case and the various decisions you may want to take depending on your constraints.
While you should always start small, load balancers would allow you to scale incrementally having architectures like this: The next important thing to take care of in your architecture is the networking itself.
This is where file systems like Ceph has already proved themselves, though considering that Ceph was not built with Kubernetes in mind and is very hard to deploy and manage, this is where a project like Rook could also help.
In this blog, we will look at the best possible way to architect your infrastructure for your use case and the various decisions you may want to take depending on your constraints.
While you should always start small, load balancers would allow you to scale incrementally having architectures like this: The next important thing to take care of in your architecture is the networking itself.
This is where file systems like Ceph has already proved themselves, though considering that Ceph was not built with Kubernetes in mind and is very hard to deploy and manage, this is where a project like Rook could also help.
Related Articles
Community Partners
DevOps Careers