Merge pull request #48 from stakater/managed-addons-argocd

ArgoCD Docs

content/managed-addons/argocd/for-administrators/availability.md

@@ -0,0 +1,25 @@
+# High Availability
+
+When configuring the ArgoCD Custom Resource within the GitOps Operator Instance Helm chart, you have the option to enable high availability for your ArgoCD instance. High availability in ArgoCD is a feature that provides redundancy and fault tolerance, ensuring continuous operation of the ArgoCD server even in the event of failures or disruptions.
+
+Enabling high availability involves setting up multiple replicas of the ArgoCD server, distributed across different nodes or availability zones in your cluster. This configuration ensures that if one replica becomes unavailable, the other replicas can continue serving requests and managing deployments without interruption.
+
+By leveraging high availability in ArgoCD, you can achieve improved reliability, scalability, and resilience for your continuous deployment workflows. It helps to mitigate the impact of server failures, network issues, or maintenance activities, ensuring uninterrupted access and management of your applications.
+
+With high availability enabled, your ArgoCD instance can handle increased traffic and workload, as requests can be distributed among the available replicas. This helps to optimize performance and responsiveness, even during peak usage periods.
+
+Moreover, high availability in ArgoCD also enhances the recovery process in case of failures. If one replica goes down, the remaining replicas can automatically take over the workload, minimizing the impact on your deployments and ensuring business continuity.
+
+The following section of YAML enables high availability in ArgoCD Custom Resource.
+
+```yaml
+    ha:
+    enabled: false
+    resources:
+      limits:
+        cpu: 500m
+        memory: 256Mi
+      requests:
+        cpu: 250m
+        memory: 128M
+```

content/managed-addons/argocd/for-administrators/installation.md

@@ -0,0 +1,29 @@
+# Installation
+
+ArgoCD is installed as part of GitOps Operator Dominator chart from `SAAP-addons` repository, along with other  managed-addons owned by Team Dominator.
+
+## Installing OpenShift GitOps Operator Chart
+
+ArgoCD can be installed seamlessly in your Red Hat OpenShift environment through the Red Hat OpenShift GitOps Operator. This operator simplifies the installation process by providing a standardized way to manage GitOps tooling, including ArgoCD.
+
+RedHat OpenShift GitOps Operator chart is available in [SAAP-addons repository](https://github.com/stakater-ab/SAAP-addons/tree/main/rh-OpenShift-GitOps-operator). By installing the Helm chart, you can quickly set up ArgoCD with default configurations and settings.
+
+During the installation process, a subscription is created to install the GitOps Operator. This subscription ensures that you have access to the latest version of the operator and can receive updates and bug fixes seamlessly. The operator is responsible for managing the ArgoCD deployment and keeping it up to date.
+
+In addition to the operator, an operator group is also installed as part of the setup. The operator group is used to define the scope and target namespace for the operator, allowing for effective management and control over the ArgoCD deployment within your OpenShift environment.
+
+By leveraging the Red Hat OpenShift GitOps Operator, installing ArgoCD becomes a streamlined process. You can easily manage and update your ArgoCD deployment while benefiting from the rich ecosystem and support provided by Red Hat and the OpenShift platform.
+
+## Installing OpenShift GitOps Instance Chart
+
+A second GitOps Operator Instance Helm chart, also available in [SAAP-addons repository](https://github.com/stakater-ab/SAAP-addons/tree/main/rh-OpenShift-GitOps-instance), installs the instance for GitOps Operator. This Helm chart enables you to customize the behavior of the operator according to your specific requirements.
+
+By installing the GitOps Operator Instance Helm chart, you create two essential Custom Resources: App Project and ArgoCD.
+
+The ArgoCD Custom Resource is particularly significant as it allows you to define various configurations for your ArgoCD instance. These configurations include the `ArgoCD-server`, which is responsible for the core functionality of ArgoCD. Additionally, you can define configurations for `Grafana` and `Prometheus`, enabling you to monitor the health and performance of your ArgoCD deployment.
+
+Furthermore, the ArgoCD Custom Resource allows you to define RBAC (Role-Based Access Control) configurations, ensuring that only authorized individuals have access to the ArgoCD instance. You can also configure the `repo-server`, which manages the synchronization of your application manifests stored in a version control repository.
+
+For high availability scenarios, the ArgoCD Custom Resource enables you to configure a `ha-server`, ensuring redundancy and fault tolerance. Finally, you can define configurations for the `controller`, which is responsible for orchestrating deployments and managing the lifecycle of your applications.
+
+By utilizing the GitOps Operator Instance Helm chart and customizing the ArgoCD Custom Resource, you have fine-grained control over the configuration and behavior of your ArgoCD instance. This empowers you to tailor ArgoCD to meet your specific deployment needs and ensures a highly efficient and secure continuous deployment workflow.

content/managed-addons/argocd/for-administrators/observability.md

@@ -0,0 +1,5 @@
+# Observability
+
+Enabling observability in the ArgoCD Custom Resource involves configuring and enabling Prometheus and Grafana, two popular monitoring and visualization tools, within your ArgoCD deployment. By enabling `prometheus` and `grafana` to "true" in the ArgoCD Custom Resource, you can activate and leverage the capabilities of Prometheus and Grafana for comprehensive observability.
+
+With Prometheus and Grafana enabled, you can leverage the power of these tools to monitor the performance and health of your ArgoCD deployment. You can gain insights into resource utilization patterns, track synchronization and deployment metrics, and identify any potential bottlenecks or issues. The visualizations and dashboards offered by Grafana allow you to easily track and analyze the collected metrics, helping you make informed decisions and take proactive measures to optimize your continuous deployment workflows.

content/managed-addons/argocd/for-administrators/resource-requirements.md

@@ -0,0 +1,13 @@
+# Resource Requirements
+
+Every time you install the Red Hat OpenShift GitOps Operator, the resources on the namespace are installed within the defined limits. If the default installation does not set any limits or requests, the Operator fails within the namespace with quotas. Without enough resources, the cluster cannot schedule ArgoCD related pods. The following table details the resource requests and limits for the default workloads:
+
+| Workloads | CPU requests | CPU limits | Memory Requests | Memory Limits |
+| --- | --- | --- | --- | --- |
+| ArgoCD-application-controller | 1 | 2 | 1024M | 2048M |
+| applicationset-controller | 1 | 2 | 512M | 1024M |
+| ArgoCD-server | 0.125 | 0.5 | 128M | 256M |
+| ArgoCD-repo-server | 0.5 | 1 | 256M | 1024M |
+| ArgoCD-redis | 0.25 | 0.5 | 128M | 256M |
+| ArgoCD-dex | 0.25 | 0.5 | 128M | 256M |
+| `HAProxy` | 0.25 | 0.5 | 128M | 256M |

content/managed-addons/argocd/overview.md

@@ -1,10 +1,14 @@
 # ArgoCD
 
-SAAP uses GitOps to continuously deliver application changes.
+## Overview
 
-[Argo CD](https://argoproj.github.io/argo-cd/) is a declarative, GitOps continuous delivery tool for Kubernetes. The deployment environment is a namespace in a container platform.
+ArgoCD is a declarative, GitOps continuous delivery tool designed to simplify and automate application deployments on Kubernetes clusters. It enables you to define the desired state of your applications and infrastructure in a Git repository, providing a robust and scalable approach to managing and deploying your applications across multiple environments.
 
-Argo CD models a collection of applications as a project and uses a Git repository to store the application's desired state.
+We use GitOps to continuously deliver application changes
+
+[ArgoCD](https://argoproj.github.io/argo-cd/) is a declarative, GitOps continuous delivery tool for Kubernetes. The deployment environment is a namespace in a container platform.
+
+ArgoCD models a collection of applications as a project and uses a Git repository to store the application's desired state.
 
 Argo CD is flexible in the structure of the application configuration represented in the Git repository.
 
@@ -17,11 +21,45 @@ Argo CD supports defining Kubernetes manifests in a number of ways:
 - plain directory of yaml/json manifests
 - custom plugins
 
-Argo CD compares the actual state of the application in the cluster with the desired state defined in Git and determines if they are out of sync. When it detects the environment is out of sync, Argo CD can be configured to either send out a notification to kick off a separate reconciliation process or Argo CD can automatically synchronize the environments to ensure they match.
+ArgoCD compares the actual state of the application in the cluster with the desired state defined in Git and determines if they are out of sync. When it detects the environment is out of sync, ArgoCD can be configured to either send out a notification to kick off a separate reconciliation process or ArgoCD can automatically synchronize the environments to ensure they match.
+
+### Benefits
+
+ArgoCD offers a wide range of powerful features that help streamline your continuous delivery workflow:
+
+1. **Declarative GitOps:** ArgoCD operates based on the GitOps principles, allowing you to define and version your application configurations in Git repositories. This declarative approach ensures consistency and reproducibility across different environments.
+
+1. **Automated Deployments:** ArgoCD automates the deployment process, continuously monitoring your Git repositories for changes and automatically applying the updates to your Kubernetes clusters. This eliminates the need for manual intervention and reduces the risk of human error.
+
+1. **Multi-Cluster and Multi-Tenancy:** ArgoCD supports managing multiple Kubernetes clusters and enables you to define different sets of applications and configurations for each cluster. It also provides support for multi-tenancy, allowing you to securely manage applications across different teams or organizations.
+
+1. **Rollbacks and Roll outs:** With ArgoCD, you can easily roll back to previous application versions or progressively roll out new versions using strategies like blue-green or canary deployments. This gives you the flexibility to test changes and ensure a smooth transition without affecting the stability of your applications.
+
+1. **Application Synchronization and Health Monitoring:** ArgoCD continuously monitors the state of your applications and performs synchronization to ensure that the desired state matches the actual state. It provides detailed insights into the health of your applications, helping you identify and resolve issues quickly.
 
-**Terminology:**
+1. **RBAC and Access Controls:** ArgoCD offers robust Role-Based Access Control (RBAC) mechanisms, allowing you to define granular permissions for different users or teams. This ensures that only authorized individuals can modify or deploy applications, maintaining the security and integrity of your deployments.
+
+### SLAs
+
+**Availability:**
+We understand the importance of high availability for continuous deployment. We guarantee a minimum monthly uptime percentage of 99.9% for the ArgoCD platform integrated into our product. This ensures that the ArgoCD service remains accessible, allowing you to effectively manage and deploy your applications without significant disruptions.
+
+**Performance:**
+Efficient performance is crucial for a smooth continuous deployment experience. Our product, powered by ArgoCD, is committed to delivering optimal performance. We guarantee an average response time of 500 milliseconds or less for typical deployment operations. This ensures that your deployment processes remain fast and responsive, facilitating efficient application delivery.
+
+**Deployment:**
+We strive to ensure successful and timely application deployments using ArgoCD. While specific deployment times can vary depending on factors such as application complexity and cluster resources, we commit to providing a reasonable deployment time frame. Rest assured, we work diligently to minimize any delays and facilitate timely application updates.
+
+**Support:**
+We are dedicated to providing exceptional support to our customers throughout their continuous deployment journey. Our support team is available to assist you with any issues or questions related to using ArgoCD in our product. For non-emergency requests, we commit to responding within one business day. In the case of critical issues that impact the deployment process or availability, we prioritize rapid response times to minimize any potential disruptions.
+
+**Service Maintenance:**
+To ensure the stability and security of our product, periodic maintenance activities may be necessary. We make every effort to schedule maintenance windows during off-peak hours to minimize any impact on your continuous deployment processes. Prior notice will be provided regarding any scheduled maintenance, allowing you to plan accordingly.
+
+### Terminology
 
 Argo CD uses a number of terms to refer to the components:
 
-- Application: A deployable unit
-- Project: A collection of applications that make up a solution
+- **Application:** In Argo CD, an application refers to a deployable unit that you want to manage and deploy in a Kubernetes cluster. It represents a specific workload, such as a microservice, a database, or any other application component that needs to be deployed. An application in Argo CD is defined using a YAML manifest file that describes its desired state, including the source code, deployment configuration, and any other resources required.
+
+- **Project:** A project in Argo CD is a logical grouping of applications that collectively form a solution or an application suite. It allows you to organize and manage multiple applications together. Projects provide a way to define access control policies and permissions at a higher level, allowing you to control who can deploy, modify, or view specific sets of applications. By grouping applications into projects, you can manage them as a cohesive unit with shared policies and settings