/explore
|
You are here 
|
gustavohidalgo.com | ||
| | | | |
martinheinz.dev
As your project grows, it might get to the point that it becomes too hard to handle with just single VM or some simple SaaS solution. You can solve tha... |
|
| | | | | ||
| | | | |
devopsdirective.com
[AI summary] The article explains how to create a maintenance page for a Kubernetes service using nginx and ConfigMaps without requiring a custom container image. |
|
| | | | | ||
| | | | |
sookocheff.com
Disaster events are one of the biggest challenges that a software organization can face. Natural disasters like earthquakes or floods, technical failures such as power or network loss, and human actions such as unauthorized attacks can disable an entire fleet of systems, leading to complete failure for a business. To deal with disaster scenarios requires a proactive approach to prepare and recover from failure. One of the key benefits of running in the cloud is how easy it is to run workloads in multiple regions. This allows you to deploy a resilient architecture that supports disaster recovery, even in the cases where an entire region is disabled. |
|
| | | | | ||
| | | | |
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. |
|
| | | |||
