Set up ArgoCD #4
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
Merged
17 tasks
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.
Our setup until now involved a lot of manual updates through the command-line, which required direct intervention from an infrastructure member, was hard to monitor, and rather error-prone. We could have set up a workflow to run the
helm installcommand for us, but this would have required exposing our servers to said workflow, and would only be a half-solution to the aforementioned pain points.ArgoCD lets us run updates based on this repository from within the cluster, and gives us a nice interface from which to monitor and interact with our resources. Furthermore, it allows us to add access to other teams in our GitHub organization, so they can themselves run basic maintainance (notably, restarts).
Most of the work to set up ArgoCD being done outside this repository, this PR adds only the manifest for an ingress route to ArgoCD's dashboard. This manifest is not strictly related to the Helm charts we distribute, but I figured it made little sense to create a whole repository to host it.