Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix!: remove the Argo CD namespace variable and hardcode the Helm release name #23

Merged
merged 3 commits into from
Jan 19, 2024

Conversation

lentidas
Copy link
Contributor

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.

⚠️ Do a Rebase and merge

Breaking change

  • Yes (in the module itself): because of the removal of the argocd_namespace variable and the fact that overloading the release name can force a recreation of the application.

Tests executed on which distribution(s)

  • EKS (AWS)

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.
Since we are hardcoding the namespace variable on all modules, the variable to set the ArgoCD namespace will no longer be needed as well.
@lentidas lentidas self-assigned this Jan 15, 2024
@lentidas lentidas requested a review from a team as a code owner January 15, 2024 13:48
@lentidas lentidas merged commit f1eb7c3 into main Jan 19, 2024
@lentidas lentidas deleted the fix/namespace_release_name branch January 19, 2024 13:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants