gitops-bridge-dev / gitops-bridge-argocd-bootstrap-terraform Goto Github PK

View Code? Open in Web Editor NEW

11.0 1.0 12.0 25 KB

Terraform module for ArgoCD bootstrap

License: Apache License 2.0

HCL 95.55% Shell 4.45%

gitops-bridge-argocd-bootstrap-terraform's Introduction

ARCHIVED REPOSITORY: Create issues and PRs in the new repository

The new location is here: https://github.com/gitops-bridge-dev/terraform-helm-gitops-bridge
The module is published on Terraform registry here: https://registry.terraform.io/modules/gitops-bridge-dev/gitops-bridge/helm/latest

gitops-bridge-argocd-bootstrap-terraform

Terraform module for gitops-bridge argocd bootstrap

It handles three aspect of ArgoCD bootstrap

Installs an intial deployment of argocd, this deployment (gets replaced by argocd applicationset)
Creates the ArgoCD cluster secret (including in-cluster)
Creates the intial set App of Apps (addons, workloads, etc.)

To be use with gitops-bridge project, see example here

Usage

locals {
  name                   = "ex-${replace(basename(path.cwd), "_", "-")}"
  environment            = "dev"
  cluster_version        = "1.27"
  gitops_addons_url      = "https://github.com/gitops-bridge-dev/gitops-bridge-argocd-control-plane-template"
  gitops_addons_basepath = ""
  gitops_addons_path     = "bootstrap/control-plane/addons"
  gitops_addons_revision = "HEAD"

  oss_addons = {
    enable_argo_workflows = true
    enable_foo                                   = true # you can add any addon here, make sure to update the gitops repo with the corresponding application set
  }
  addons = merge(local.oss_addons, { kubernetes_version = local.cluster_version })

  addons_metadata = merge(
    {
      addons_repo_url      = local.gitops_addons_url
      addons_repo_basepath = local.gitops_addons_basepath
      addons_repo_path     = local.gitops_addons_path
      addons_repo_revision = local.gitops_addons_revision
    }
  )

  argocd_apps = {
    addons = file("${path.module}/bootstrap/addons.yaml")
    workloads = file("${path.module}/bootstrap/workloads.yaml")
  }

}

################################################################################
# GitOps Bridge: Bootstrap
################################################################################
module "gitops_bridge_bootstrap" {
  source = "github.com/gitops-bridge-dev/gitops-bridge-argocd-bootstrap-terraform?ref=v2.0.0"

  cluster = {
    cluster_name = local.name
    environment  = local.environment
    metadata     = local.addons_metadata
    addons       = local.addons
  }
  apps = local.argocd_apps
}

Requirements

Name	Version
terraform	>= 1.0
helm	>= 2.10.1
kubernetes	>= 2.22.0

Providers

Name	Version
helm	>= 2.10.1
kubernetes	>= 2.22.0

Modules

No modules.

Resources

Name	Type
helm_release.argocd	resource
helm_release.bootstrap	resource
kubernetes_secret_v1.cluster	resource

Inputs

Name	Description	Type	Default	Required
apps	argocd app of apps to deploy	`any`	`{}`	no
argocd	argocd helm options	`any`	`{}`	no
cluster	argocd cluster secret	`any`	`null`	no
create	Create terraform resources	`bool`	`true`	no
install	Deploy argocd helm	`bool`	`true`	no

Outputs

Name	Description
apps	ArgoCD apps
argocd	Argocd helm release
cluster	ArgoCD cluster

gitops-bridge-argocd-bootstrap-terraform's People

Contributors

Stargazers

Watchers

Forkers

allamand jihed devops-corner malikdraz luong-komorebi mlasalmo gargp1 eddimull vtodankar hamedouk markoskandylis yougotagift

gitops-bridge-argocd-bootstrap-terraform's Issues

Publish the module to the terraform registry

is this ready for usage?

Thanks for making this! Much cleaner to have the bootstrap in its own repo. I was in the middle of configuring our code with the old bootstrap module when I noticed this one. Is this ready to use?

Something wrong with bootstrap yaml file rendering

./bootstrap/addons.yaml

apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
  name: addons
  namespace: argocd
spec:
  destination:
    server: https://kubernetes.default.svc
  project: system
  source:
    helm:
      values: |
        "account": "{{metadata.annotations.aws_account_id}}"
        "clusterName": "{{metadata.annotations.cluster_name}}"
        "region": "{{metadata.annotations.aws_region}}"
        "repoUrl": "{{metadata.annotations.addons_repo_revision}}"
    path: '{{metadata.annotations.addons_repo_path}}' #chart
    repoURL: '{{metadata.annotations.addons_repo_url}}'
    targetRevision: '{{metadata.annotations.addons_repo_revision}}'
  syncPolicy:
    retry:
      backoff:
        duration: 10s
        factor: 2
        maxDuration: 3m
      limit: 10
    syncOptions:
      - Validate=false
      - CreateNamespace=true
      - PrunePropagationPolicy=foreground
      - PruneLast=true
      - ServerSideApply=true
      - RespectIgnoreDifferences=true

all of the metadata.annotations are successfully created as secret.

Remove prefix argocd_ from variables names

terraform apply reverts argocd config from gitops

When running terraform apply, any changes done via gitops from application set are reverted momentary

You can see the LoadBalancer being reverted to ClusterIP for the argocd-server svc

Error applying several bootstraps with terraform

While working with the cluster, sometimes, Terraform is not able to apply the manifest due to fetch error:

│ Error: argocd/bootstrap-addons failed to fetch resource from kubernetes: the server could not find the requested resource
│ 
│   with module.eks_cluster.module.gitops_bridge_bootstrap.kubectl_manifest.bootstrap["addons"],
│   on .terraform/modules/eks_cluster.gitops_bridge_bootstrap/main.tf line 93, in resource "kubectl_manifest" "bootstrap":
│   93: resource "kubectl_manifest" "bootstrap" {
│

This seems to be related to gavinbunney/terraform-provider-kubectl#270

One of the suggested workaround, is to relay on a raw helm chart to apply the manifest

Merge metadata module into bootstrap module

Merge the functionality of metadata https://github.com/gitops-bridge-dev/gitops-bridge-argocd-metadata-terraform