Repository navigation
feat(gitops): rollout de imagem via Argo CD Image Updater - #14
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
O que muda
Substitui o mecanismo de rollout de imagem: em vez do CI abrir um PR bumpando o digest no
values-development.yaml(fricção real, ambientedevelopmentnão deveria exigir aprovação humana pra atualizar sozinho), o Argo CD Image Updater passa a observar o registry e aplicar a atualização direto naApplication, sem commit..github/workflows/build-push.dev.yml: revertido pro original (o Image Updater não precisa de nenhum passo novo no CI).gitops/envs/development/applications/docs.yaml: anotaçõesargocd-image-updater.argoproj.io/*(image-list, update-strategy digest, write-back-method argocd).Depende do PR companheiro em
ladesa-ro/infrastructureque instala o Image Updater (referenciado ali).Test plan
helm templatelocal confirmando queapplication.deployment.image.digesté aceito pelo chart.Applicationreflete o digest atual e que um push novo atualiza o pod sozinho.