« ArgoCD - GitOps » : différence entre les versions
m (→GitOps) |
m (→GitOps) |
||
| Ligne 2 : | Ligne 2 : | ||
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. | 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. | ||
== Why not CI/CD or CLI == | |||
Engineer decides not to use '''CI/CD''' for deploying their code on the Kubernetes cluster because it '''requires exposing credentials'''. Even though '''solutions exist to secure''' credentials, it is still generally '''not recommended'''. As for using the '''CLI''', the '''issue''' is that '''modifications are made directly''' in the infrastructure. If these changes are '''not pushed to Git''', they '''risk being overwritten''' by the code from the repository. So it's why we decide to use GitOps methodology. | Engineer decides not to use '''CI/CD''' for deploying their code on the Kubernetes cluster because it '''requires exposing credentials'''. Even though '''solutions exist to secure''' credentials, it is still generally '''not recommended'''. As for using the '''CLI''', the '''issue''' is that '''modifications are made directly''' in the infrastructure. If these changes are '''not pushed to Git''', they '''risk being overwritten''' by the code from the repository. So it's why we decide to use GitOps methodology. | ||
== Principles == | |||
= ArgoCD = | = ArgoCD = | ||
Version du 4 février 2025 à 22:05
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.
Why not CI/CD or CLI
Engineer decides not to use CI/CD for deploying their code on the Kubernetes cluster because it requires exposing credentials. Even though solutions exist to secure credentials, it is still generally not recommended. As for using the CLI, the issue is that modifications are made directly in the infrastructure. If these changes are not pushed to Git, they risk being overwritten by the code from the repository. So it's why we decide to use GitOps methodology.