Skip to content

Conversation

@jaygridley
Copy link
Member

@jaygridley jaygridley commented May 16, 2025

Description

Type of change

  • A bug fix (PR prefix fix)
  • A new feature (PR prefix feat)
  • A code change that neither fixes a bug nor adds a feature (PR prefix refactor)
  • Adding missing tests or correcting existing tests (PR prefix test)
  • Changes that do not affect the meaning of the code like white-spaces, formatting, missing semi-colons, etc. (PR prefix style)
  • Changes to our CI configuration files and scripts (PR prefix ci)
  • Documentation only changes (PR prefix docs)

This PR migrates addon structure to the https://github.com/lablabs/terraform-aws-eks-universal-addon template.

Breaking Changes

  • Variable irsa_assume_role_arn was renamed to irsa_assume_role_arns and changing its type from string to list(string).
  • Variable storage_accounts was replaces by individual SA variables, i.e. application_controller_service_account_create, application_controller_service_account_name etc.
  • When upgrading to this version of addon and using self-managed installation a new variable value self_managed_helm_release_name must be provided. It is also advised to set a different name for ArgoCD Application Helm release to avoid collision with self-managed Helm release and patch Helm release name ArgoCD Application uses for it release by specifying
  self_managed_helm_release_name = "argocd"
  helm_release_name              = "argocd-application" # a different name to avoid collision with the self-managed Helm release

  argo_spec = {
    source = {
      helm = {
        releaseName = "argocd" # override the release name to addopt resources created by the self-managed Helm release
      }
    }
  }
  • When upgrading to this version you can expect recreation of existing IAM role due to name changes. Also, more roles will be created as now we have a dedicated role for each ArgoCD component.
  • ArgoCD Helm chart and application were updated to 7.8.23, 2.14.9 respectively. Follow upgrade guides 1, 2 to migrate your configurations.

How Has This Been Tested?

  • Upgrade path
  • Re-creating with self-managed installation

@jaygridley jaygridley self-assigned this May 16, 2025
@jaygridley jaygridley requested a review from atyu1 May 16, 2025 12:22
Copy link

@atyu1 atyu1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please review my comments

@jaygridley jaygridley requested a review from atyu1 May 16, 2025 13:12
@jaygridley jaygridley requested a review from atyu1 May 19, 2025 08:46
Copy link

@atyu1 atyu1 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM

@jaygridley jaygridley merged commit 2a7e92c into main May 19, 2025
5 checks passed
@jaygridley jaygridley deleted the feat/universal-addon-migration branch June 3, 2025 09:42
@jaygridley jaygridley changed the title feat: universal-addon migration feat!: universal-addon migration Jun 3, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants