« ArgoCD - GitOps » : différence entre les versions
Aller à la navigation
Aller à la recherche
mAucun résumé des modifications |
(→GitOps) |
||
| Ligne 1 : | Ligne 1 : | ||
= GitOps = | = GitOps = | ||
The term '''GitOps''' refers to the '''practice of deploying''' a '''pipeline''' that '''connects''' your '''repository''' (GitLab) to your '''Kubernetes cluster'''. Whenever a '''change is made''' in the repository, it is then '''sent to''' a '''pipeline''' like '''ArgoCD''', which '''applies''' the '''change''' to the '''Kubernetes cluster'''. In the CI/CD concept, GitOps is concerned only with '''CD (Continuous Delivery)''', but it remains distinct from traditional CI/CD and should not be confused with it. | The term '''GitOps''' refers to the '''practice of deploying''' a '''pipeline''' that '''connects''' your '''repository''' (GitLab) to your '''Kubernetes cluster''' in order to do Infrastructure as Code (or Policy as Code, Network as Code, etc.). Whenever a '''change is made''' in the repository, it is then '''sent to''' a '''pipeline''' like '''ArgoCD''', which '''applies''' the '''change''' to the '''Kubernetes cluster'''. In the CI/CD concept, GitOps is concerned only with '''CD (Continuous Delivery)''', but it remains distinct from traditional CI/CD and should not be confused with it. | ||
= ArgoCD = | = ArgoCD = | ||
Version du 4 février 2025 à 21:38
GitOps
The term GitOps refers to the practice of deploying a pipeline that connects your repository (GitLab) to your Kubernetes cluster in order to do Infrastructure as Code (or Policy as Code, Network as Code, etc.). Whenever a change is made in the repository, it is then sent to a pipeline like ArgoCD, which applies the change to the Kubernetes cluster. In the CI/CD concept, GitOps is concerned only with CD (Continuous Delivery), but it remains distinct from traditional CI/CD and should not be confused with it.