Explore >> Select a destination
|
You are here 
|
earthly.dev | ||
| | | | |
devopsian.net
|
|
| | | | | A deep-dive into progressive deployments, specifically Canary, on Kubernetes with Flagger using ingress-controller or a service mesh. How it works? I ran into some pitfalls and wrote about it, so you don't need to solve it too. | |
| | | | |
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. | |
| | | | |
vadosware.io
|
|
| | | | | I set up statping for a few websites I maintain on my small k8s cluster | |
| | | | |
nts.strzibny.name
|
|
| | | Here's one way of a cloud-independent deployment of Rails, Sidekiq, PostgreSQL, and Redis on single virtual server with Kamal. | ||
