/explore
|
You are here 
|
nodogmablog.bryanhogan.net | ||
| | | | |
www.learnitguide.net
|
|
| | | | | kubernetes yaml file examples, create kubernetes deployment examples, create kubernetes service examples, create kubernetes pods examples, create yaml | |
| | | | |
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.nuculabs.de
|
|
| | | | | Hi ?, In this article I will talk about how to authenticate your applications to the Kubernetes API via the service accounts feature. Citing the Kubernetes docs, a service account for a pod: "provides an identity for processes that run in a Pod. When you (a human) access the cluster (for example, using kubectl), you are authenticated by the apiserver as a particular User Account (currently this is usually admin, unless your cluster administrator has customized your cluster). Processes in containers inside pods can also contact the apiserver. When they do, they are authenticated as a particular Service Account (for example, default)." | |
| | | | |
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. | ||
