Add cozy update workflow #5
Merged
Conversation
This file contains 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.
The current setup for Cozy involves bypassing Kubernetes' image cache and restarting the pod after every update so that the new
latestimage can be used. This requires an action from the infra team, makes every restart a tiny bit slower, wastes some bandwidth, and prevents rollbacks.Now with #4 reducing the necessity for manual actions, it was time to have some mechanism that allows Cozy updates to be picked up and logged by relevant tooling.
This PR lays the groundwork for automated versioned updates of the Cozy chart. The next steps involve enabling automated sync for the quilt-cozy application in ArgoCD, and adding a workflow to the Cozy repository to trigger a repository_dispatch event when pushing to the main branch.