From 7c3e36fe405989461b4cffe522a0428d3fdb3f84 Mon Sep 17 00:00:00 2001 From: Samuel Maftoul Date: Tue, 20 Sep 2022 09:16:12 +0200 Subject: [PATCH] Remove duplicated question in ArgoCD (#296) --- topics/argo/README.md | 11 +---------- 1 file changed, 1 insertion(+), 10 deletions(-) diff --git a/topics/argo/README.md b/topics/argo/README.md index 927da12..ee6cb84 100644 --- a/topics/argo/README.md +++ b/topics/argo/README.md @@ -73,15 +73,6 @@ It's the repository that holds app configuration, the one updated most of the ti
What are the advantages in using GitOps approach/repository?
-* Your whole configuration is one place, defined as code so it's completely transparent, adjustable for changes and easily reproducible -* Everyone go through the same interface hence you have more people experiencing and testing the code, even if not intentionally -* Engineers can use it for testing, development, ... there is no more running manual commands and hoping to reach the same status as in the cluster/cloud. -* -
- -
-What are the advantages in using GitOps approach/repository?
- * Your whole configuration is one place, defined as code so it's completely transparent, adjustable for changes and easily reproducible * Everyone go through the same interface hence you have more people experiencing and testing the code, even if not intentionally * Engineers can use it for testing, development, ... there is no more running manual commands and hoping to reach the same status as in the cluster/cloud. @@ -185,4 +176,4 @@ There are multiple ways to deal with it: Instead of creating Kubernetes resources, you can use Git to manage who is allowed to push code, to review it, merge it, etc - either human users or 3rd party systems and services. There is no need to use ClusterRole or User resources in Kubernetes hence the management of access is much more simplified. -
\ No newline at end of file +