From 2b60666477256cb393cd8b9ed228ca671fea216e Mon Sep 17 00:00:00 2001 From: Itamar Ben Yair Date: Thu, 7 Apr 2022 10:46:24 +0300 Subject: [PATCH] Added a blog post about ArgoCD best practices --- docs/argocd.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/docs/argocd.md b/docs/argocd.md index 6c5433f9..940a7b86 100644 --- a/docs/argocd.md +++ b/docs/argocd.md @@ -29,6 +29,7 @@ - [==faun.pub: Manage Prometheus alerting and recording rules using GitOps==](https://faun.pub/manage-prometheus-alerting-and-recording-rules-using-gitops-6c19bd1fd50) - [medium.com/containers-101: Using GitOps, Multiple Argo Instances, and Environments with Argo CD at Scale](https://medium.com/containers-101/using-gitops-multiple-argo-instances-and-environments-with-argo-cd-at-scale-e6b19c86be36) - [blog.argoproj.io: Architecting Workflows For Reliability](https://blog.argoproj.io/architecting-workflows-for-reliability-d33bd720c6cc) Kubernetes is designed for stateless scalable web applications, apps where if one process dies, then another process can be dropped in its place. Kubernetes makes one promise — it will kill your pods. Kubernetes expects applications built on it to be tolerant of both any disruption— so apps must be designed with that in mind. +- [datree.io: ArgoCD Best Practices](https://datree.io/resources/argocd-best-practices-you-should-know) ``` Dear user, @@ -80,4 +81,4 @@ - \ No newline at end of file +