Repos-que-me-gustan/devops-exercises
1
0
Fork 0
Code Pull Requests Activity

Remove duplicated question in ArgoCD (#296)

Browse Source
This commit is contained in:
Samuel Maftoul 2022-09-20 09:16:12 +02:00 committed by GitHub
parent f4a402a90f
commit 7c3e36fe40
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 1 additions and 10 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

11
topics/argo/README.md
View File

@ -73,15 +73,6 @@ It's the repository that holds app configuration, the one updated most of the ti
<details>
<summary>What are the advantages in using GitOps approach/repository?</summary><br><b>
* 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.
*
</b></details>
<details>
<summary>What are the advantages in using GitOps approach/repository?</summary><br><b>
* 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.
</b></details>
</b></details>