Explore >> Select a destination
|
You are here 
|
gustavohidalgo.com | ||
| | | | |
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. | |
| | | | |
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. | |
| | | | |
blog.zespre.com
|
|
| | | The dockershim has been announced as deprecated since Kubernetes v1.20. And Kubernetes v1.23 is about to step into its EOL after the end of this month. So its time to move forward! Lets upgrade the cluster to v1.24. This article is solely for the personal record about changing container runtimes to upgrade Kubernetes from v1.23 to v1.24. | ||
