The Art of GitOps: Rendered Manifests - Christian Hernandez, Akuity

Поділитися
Вставка
  • Опубліковано 29 січ 2025

КОМЕНТАРІ • 10

  • @Muaahaa
    @Muaahaa Рік тому +1

    ArgoCD diffs can be generated as part of CI checks and included in PRs. This will show you the actual changes to rendered manifests.

    • @okitsalex
      @okitsalex Рік тому

      The issue is your CI agent now needs access to argo and that kind of violates Gitops no?

    • @Muaahaa
      @Muaahaa Рік тому

      ​@@okitsalexI don't think so. ArgoCD has an RBAC system. You just give your CI runners read access needed to do diff. GitOps is concerned with write access to your cluster.

    • @okitsalex
      @okitsalex Рік тому

      @@Muaahaa do you need access to the cluster as well?

    • @Muaahaa
      @Muaahaa Рік тому

      ​@@okitsalexYou need network access to ArgoCD's API. If that isn't something you are able to expose for regulatory reasons then won't be a feasible option. You do *not* need access to the K8S control plane, though.

    • @okitsalex
      @okitsalex Рік тому

      That makes sense, thanks!
      @@Muaahaa

  • @east4ming
    @east4ming Рік тому

    Am I right in understanding that you're duplicating a wheel like terraform, and the second git repository is the state file of terraform.

  • @joebowbeer
    @joebowbeer Рік тому +1

    5:01 Store rendered manifests (aka build artifacts) in an OCI registry, along with images and other artifacts. Using git branches is an unnecessary hack.

  • @MikaelFridh
    @MikaelFridh Рік тому

    Manifests in Git Branches, Git folders, OCI? It's just "Storage your deployment controller can read from". Use what gives the most benefits (visibility, tracking etc). Ie, OCI is probably NOT IT today.