Argocd Architecture Doc

Package Merge Request

Package Changes

Create argocd architecture documentation

Doc preview: https://repo1.dso.mil/platform-one/big-bang/bigbang/-/blob/argocd-architecture-doc/docs/understanding-bigbang/package-architecture/argocd.md

For Issue

Closes https://repo1.dso.mil/platform-one/big-bang/apps/core/argocd/-/issues/53

docs/understanding-bigbang/package-architecture/argocd.md

@@ -74,23 +74,27 @@ High Availability installation is recommended for production use. This bundle in
 
 - [ha/namespace-install.yaml](https://github.com/argoproj/argo-cd/blob/master/manifests/ha/namespace-install.yaml) - the same as namespace-install.yaml but with multiple replicas for supported components.
 
-For additional information about an ArgoCD high availability installation visit [ArgoCD High Availability](https://argo-cd.readthedocs.io/en/stable/operator-manual/installation/#high-availability)
+The following is an example of how to modify the Big Bang values to accommodate a HA deployment.
 
 ```yaml
 addons:
   argocd:
     values:
-      application-controller:
-        replicas:
+      controller:
+        replicas: 2
       server:
-        replicas:    
+        replicas: 2  
       repoServer:
-        replicas:                
+        replicas: 2              
 ```
 
+_Note:_ A production HA deployment of argocd within Big Bang has not yet been produced and results may vary.
+
+For additional information about an ArgoCD high availability installation visit [ArgoCD High Availability](https://argo-cd.readthedocs.io/en/stable/operator-manual/installation/#high-availability)
+
 ### UI
 
-ArgoCD includes a UI, which is accessible at the specified URL. The UI can be used to view, manage, and reate applications.
+ArgoCD includes a UI, which is accessible at the specified URL. The UI can be used to view, manage, and create applications.
 
 ### Logging
 
@@ -98,6 +102,27 @@ Argo CD logs payloads of most API requests except request that are considered se
 
 _Note:_ within Big Bang, logs are captured by fluentbit and shipped to elastic by default.
 
+```yaml
+addons:
+  argocd:
+    values:
+      controller:
+        # -- Set the logging level. (One of: `debug`, `info`, `warn`, `error`)
+        logLevel: debug
+        # -- Application controller log format. Either `text` or `json`
+        logFormat: text
+      server:
+        # -- Set the logging level. (One of: `debug`, `info`, `warn`, `error`)
+        logLevel: debug
+        # -- Application controller log format. Either `text` or `json`
+        logFormat: text    
+      repoServer:
+        # -- Set the logging level. (One of: `debug`, `info`, `warn`, `error`)
+        logLevel: debug
+        # -- Application controller log format. Either `text` or `json`
+        logFormat: text           
+```
+
 ### Monitoring
 
 ArgoCD exposes prometheus metrics in the API of each service if the config.yaml used by that service has the metrics.enabled keys set to enabled and metrics.servicemonitor keys set to true. Each service exports its own metrics and is typically scraped by a Prometheus installation to gather the metrics.