fix!: remove the Argo CD namespace variable and hardcode the Helm release name #23
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.
Description of the changes
The main changes of this PR are the following:
fix!: hardcode the release name to remove the destination cluster
I found out that Argo CD passes the name of the application as a value to set the Helm chart. This means that all the templating that used
{ $.Release.Name }
would resolve to the name given to Argo CD application.In a multicluster deployment, using a single Argo CD, the names of the applications must be different. We solved that by appending the cluster name to the default application name when deploying on different clusters than
in-cluster
. However, this resulted in multiple problems for deployments that depended on the name of the application being static, so this solves that.This is a breaking change because sometimes this requires an application to be deleted and recreated.
fix!: remove the ArgoCD namespace variable
Since we are hardcoding the namespace variable on all modules, the variable to set the ArgoCD namespace will no longer be needed as well.
Breaking change
argocd_namespace
variable and the fact that overloading the release name can force a recreation of the application.Tests executed on which distribution(s)