ArgoCD + Big Bang Redis

Summary

ArgoCD proposed changes to have BigBang Redis be used for HA via adding it as the HA dependency: https://repo1.dso.mil/platform-one/big-bang/apps/core/argocd/-/merge_requests/23

changed milestone to %1.3.0

added argocd label

Deployed with the values file:

addons:
  argocd:
    enabled: true
    git:
      tag: ""
      branch: "redis"

We need to have a discussion about how redis will be implemented
https://repo1.dso.mil/platform-one/big-bang/bigbang/-/issues/263
Redis should be a BigBang addon that other addons can reference as a dependency. A similar strategy as minio.
Hacking upstream charts to add a redis subchart does not seem like a good strategy. Most charts already support pointing to an external redis. Let BigBang handle the integration.

added 1 commit

• 2cfeff44 - argocd tag bump

Compare with previous version

resolved all threads

added 1 commit

• 4b608307 - modifying for new scheme

Compare with previous version

added 44 commits

• 4b608307...92ca3c9f - 43 commits from branch master
• 4d4e647d - resolving conflicts

Compare with previous version

added statusdoing label

changed milestone to %1.4.0

added statusreview label and removed statusdoing label

marked this merge request as ready

#250 (closed)

mentioned in issue #228 (closed)

added 1 commit

• e6f826e3 - enable istio by default

Compare with previous version

mentioned in merge request !348 (closed)

added 1 commit

• 06e646cd - modify to take value from top level chart

Compare with previous version

added 1 commit

• c1fd3030 - argo tag bump

Compare with previous version

added 19 commits

• c1fd3030...8bb1fd75 - 18 commits from branch master
• cefd0f2a - ArgoCD BB Redis

Compare with previous version

added 3 commits

• cefd0f2a...97c1f8ba - 2 commits from branch master
• cf8267a8 - Argo Tag Bump

Compare with previous version

approving and merging even though upgrade is failing because current argocd doesn't have a virtualservice deployed, this fixes that

approved this merge request

merged

mentioned in commit b71158a6

mentioned in issue #324 (closed)

mentioned in issue #634 (closed)