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

Add questions on ArgoCD

Browse Source 
As well as on other topics.
This commit is contained in:
abregman
2022-09-14 21:39:47 +03:00
parent 3d129216e0
commit e56bf576df
7 changed files with 243 additions and 46 deletions
Download Patch File Download Diff File Expand all files Collapse all files

9
topics/devops/README.md
View File

@@ -433,6 +433,7 @@ Read more [here](https://about.gitlab.com/topics/gitops)
* It introduces limited/granular access to infrastructure
* It makes it easier to trace who makes changes to infrastructure
</b></details>
<details>
@@ -442,6 +443,14 @@ Read more [here](https://about.gitlab.com/topics/gitops)
* Apply review/approval process for changes
</b></details>
<details>
<summary>Two engineers in your team argue on where to put the configuration and infra related files of a certain application. One of them suggests to put it in the same repo as the application repository and the other one suggests to put to put it in its own separate repository. What's your take on that?</summary><br><b>
One might say we need more details as to what these configuration and infra files look like exactly and how complex the application and its CI/CD pipeline(s), but in general, most of the time you will want to put configuration and infra related files in their own separate repository and not in the repository of the application for multiple reasons:
* Every change submitted to the configuration, shouldn't trigger the CI/CD of the application, it should be testing out and applying the modified configuration
</b></details>
#### SRE
<details>