Explore >> Select a destination
|
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... | |
| | | | |
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. | |
| | | | |
foo.zone
|
|
| | | | | [AI summary] The text describes a comprehensive setup of a Kubernetes cluster (k3s) with various services and tools. It includes a private Docker registry, multiple applications like Anki Sync Server, Miniflux, and others, all utilizing NFS storage and UID/GID mapping for compatibility. The setup also involves relayd for traffic routing, Ingress controllers, and custom Helm charts for deployment. The author plans to expand on monitoring and observability in future posts. | |
| | | | |
jb3.dev
|
|
| | | AlertManager is a rock solid approach for alerting in Prometheus, but how do you make it highly available on Kubernetes? This article covers my approach to making AlertManager highly available on Kubernetes, and how you can do the same. | ||
