Merge pull request #65250 from Srivaralakshmi/switchover-gitops-to-standalone

Switchover GitOps to standalone

Author: gabriel-rh

_topic_maps/_topic_map.yml

@@ -1911,50 +1911,8 @@ Topics:
   Dir: gitops
   Distros: openshift-enterprise
   Topics:
-  - Name: OpenShift GitOps release notes
-    File: gitops-release-notes
-  - Name: Understanding OpenShift GitOps
-    File: understanding-openshift-gitops
-  - Name: Installing OpenShift GitOps
-    File: installing-openshift-gitops
-  - Name: Uninstalling OpenShift GitOps
-    File: uninstalling-openshift-gitops
-  - Name: Setting up a new Argo CD instance
-    File: setting-up-argocd-instance
-  - Name: Monitoring Argo CD instances
-    File: monitoring-argo-cd-instances
-  - Name: Using Argo Rollouts for progressive deployment delivery
-    File: using-argo-rollouts-for-progressive-deployment-delivery
-  - Name: Configuring an OpenShift cluster by deploying an application with cluster configurations
-    File: configuring-an-openshift-cluster-by-deploying-an-application-with-cluster-configurations
-  - Name: Deploying a Spring Boot application with Argo CD
-    File: deploying-a-spring-boot-application-with-argo-cd
-  - Name: Argo CD custom resource properties
-    File: argo-cd-custom-resource-properties
-  - Name: Configuring secure communication with Redis
-    File: configuring-secure-communication-with-redis
-  - Name: Monitoring application health status
-    File: health-information-for-resources-deployment
-  - Name: Configuring SSO for Argo CD using Dex
-    File: configuring-sso-on-argo-cd-using-dex
-  - Name: Configuring SSO for Argo CD using Keycloak
-    File: configuring-sso-for-argo-cd-using-keycloak
-  - Name: Configuring Argo CD RBAC
-    File: configuring-argo-cd-rbac
-  - Name: Configuring Resource Quota
-    File: configuring-resource-quota
-  - Name: Monitoring Argo CD custom resource workloads
-    File: monitoring-argo-cd-custom-resource-workloads
-  - Name: Viewing Argo CD logs
-    File: viewing-argo-cd-logs
-  - Name: Running Control Plane Workloads on Infra nodes
-    File: run-gitops-control-plane-workload-on-infra-nodes
-  - Name: Sizing requirements for GitOps Operator
-    File: about-sizing-requirements-gitops
-  - Name: Collecting debugging data for a support case
-    File: collecting-debugging-data-for-support
-  - Name: Troubleshooting issues in GitOps
-    File: troubleshooting-issues-in-GitOps
+  - Name: About OpenShift GitOps
+    File: about-redhat-openshift-gitops
 - Name: Jenkins
   Dir: jenkins
   Distros: openshift-enterprise

cicd/gitops/about-redhat-openshift-gitops.adoc

@@ -0,0 +1,54 @@
+:_content-type: ASSEMBLY
+include::_attributes/common-attributes.adoc[]
+[id="about-redhat-openshift-gitops"]
+= About {gitops-title}
+:context: about-redhat-openshift-gitops
+
+toc::[]
+
+{gitops-title} is an Operator that uses Argo CD as the declarative GitOps engine. It enables GitOps workflows across multicluster OpenShift and Kubernetes infrastructure. Using {gitops-title}, administrators can consistently configure and deploy Kubernetes-based infrastructure and applications across clusters and development lifecycles. {gitops-title} is based on the open source project link:https://argoproj.github.io/cd/[Argo CD] and provides a similar set of features to what the upstream offers, with additional automation, integration into Red Hat {OCP} and the benefits of Red Hat’s enterprise support, quality assurance and focus on enterprise security.
+
+[NOTE]
+====
+Because {gitops-title} releases on a different cadence from {OCP}, the {gitops-title} documentation is now available as separate documentation sets for each minor version of the product. 
+
+The {gitops-title} documentation is available at link:https://docs.openshift.com/gitops/[].
+
+Documentation for specific versions is available using the version selector dropdown, or directly by adding the version to the URL, for example, link:https://docs.openshift.com/gitops/1.8[].
+
+In addition, the {gitops-title} documentation is also available on the Red Hat Portal at https://access.redhat.com/documentation/en-us/red_hat_openshift_gitops/[].
+
+For additional information about the {gitops-title} life cycle and supported platforms, refer to the link:https://access.redhat.com/support/policy/updates/openshift#gitops[Platform Life Cycle Policy].
+====
+
+{gitops-title} ensures consistency in applications when you deploy them to different clusters in different environments, such as: development, staging, and production. {gitops-title} organizes the deployment process around the configuration repositories and makes them the central element. It always has at least two repositories:
+
+  . Application repository with the source code
+  . Environment configuration repository that defines the desired state of the application
+
+These repositories contain a declarative description of the infrastructure you need in your specified environment. They also contain an automated process to make your environment match the described state.
+
+{gitops-title} uses Argo CD to maintain cluster resources. Argo CD is an open-source declarative tool for the continuous integration and continuous deployment (CI/CD) of applications. {gitops-title} implements Argo CD as a controller so that it continuously monitors application definitions and configurations defined in a Git repository. Then, Argo CD compares the specified state of these configurations with their live state on the cluster.
+
+Argo CD reports any configurations that deviate from their specified state. These reports allow administrators to automatically or manually resync configurations to the defined state. Therefore, Argo CD enables you to deliver global custom resources, like the resources that are used to configure {OCP} clusters.
+
+[id="key-features"]
+== Key features
+
+{gitops-title} helps you automate the following tasks:
+
+* Ensure that the clusters have similar states for configuration, monitoring, and storage
+* Apply or revert configuration changes to multiple {OCP} clusters
+* Associate templated configuration with different environments
+* Promote applications across clusters, from staging to production
+
+// add something about CLI tools?
+
+
+[id="additional-resources_about-op-gitops"]
+[role="_additional-resources"]
+== Additional resources
+
+* link:https://docs.openshift.com/container-platform/latest/operators/understanding/crds/crd-extending-api-with-crds.html#crd-extending-api-with-crds[Extending the Kubernetes API with custom resource definitions]
+* link:https://docs.openshift.com/container-platform/latest/operators/understanding/crds/crd-managing-resources-from-crds.html#crd-managing-resources-from-crds[Managing resources from custom resource definitions]
+* link:https://docs.openshift.com/gitops/latest/understanding_openshift_gitops/what-is-gitops.html#what-is-gitops[What is GitOps?]

cicd/index.adoc

@@ -35,7 +35,7 @@ For more information, see xref:https://docs.openshift.com/pipelines/latest/about
 == OpenShift GitOps
 OpenShift GitOps is an Operator that uses Argo CD as the declarative GitOps engine. It enables GitOps workflows across multicluster OpenShift and Kubernetes infrastructure. Using OpenShift GitOps, administrators can consistently configure and deploy Kubernetes-based infrastructure and applications across clusters and development lifecycles.
 
-For more information, see xref:../cicd/gitops/understanding-openshift-gitops.adoc#understanding-openshift-gitops[Understanding OpenShift GitOps]
+For more information, see xref:../cicd/gitops/about-redhat-openshift-gitops.adoc#about-redhat-openshift-gitops[About {gitops-title}].
 
 [id="jenkins-ci-cd"]
 == Jenkins

scalability_and_performance/ztp_far_edge/ztp-preparing-the-hub-cluster.adoc

@@ -22,7 +22,7 @@ include::modules/ztp-acm-installing-disconnected-rhacm.adoc[leveloffset=+1]
 [role="_additional-resources"]
 .Additional resources
 
-* xref:../../cicd/gitops/installing-openshift-gitops.adoc#getting-started-with-openshift-gitops[Installing OpenShift GitOps]
+* link:https://docs.openshift.com/gitops/latest/installing_gitops/installing-openshift-gitops.html#installing-openshift-gitops[Installing OpenShift GitOps]
 
 * xref:../../scalability_and_performance/ztp_far_edge/cnf-talm-for-cluster-upgrades.adoc#installing-topology-aware-lifecycle-manager-using-cli_cnf-topology-aware-lifecycle-manager[Installing {cgu-operator}]
 

welcome/index.adoc

@@ -185,7 +185,7 @@ Pipelines use standard Tekton custom resources to automate deployments and are d
 
 ifdef::openshift-enterprise,openshift-webscale,openshift-origin[]
 
-- **xref:../cicd/gitops/understanding-openshift-gitops.adoc#understanding-openshift-gitops[Manage your infrastructure and application configurations]**: GitOps is a declarative way to implement continuous deployment for cloud native applications. GitOps defines infrastructure and application definitions as code. GitOps uses this code to manage multiple workspaces and clusters to simplify the creation of infrastructure and application configurations. GitOps also handles and automates complex deployments at a fast pace, which saves time during deployment and release cycles.
+- **link:https://docs.openshift.com/gitops/latest/understanding_openshift_gitops/about-redhat-openshift-gitops.html#about-redhat-openshift-gitops[Manage your infrastructure and application configurations]**: GitOps is a declarative way to implement continuous deployment for cloud native applications. GitOps defines infrastructure and application definitions as code. GitOps uses this code to manage multiple workspaces and clusters to simplify the creation of infrastructure and application configurations. GitOps also handles and automates complex deployments at a fast pace, which saves time during deployment and release cycles.
 
 - **xref:../applications/working_with_helm_charts/configuring-custom-helm-chart-repositories.adoc#installing-a-helm-chart-on-an-openshift-cluster_configuring-custom-helm-chart-repositories[Deploy Helm charts]**:
 xref:../applications/working_with_helm_charts/understanding-helm.adoc#understanding-helm[Helm] is a software package manager that simplifies deployment of applications and services to {product-title} clusters. Helm uses a packaging format called _charts_. A Helm chart is a collection of files that describes the {product-title} resources.