Update side-by-side content

NimRegev · NimRegev · commit 779a9994a56a · 2023-09-05T11:40:56.000+03:00
Updated minor version sync content acc to Ilia's feedback
diff --git a/_docs/installation/behind-the-firewall.md b/_docs/installation/behind-the-firewall.md
@@ -1,5 +1,6 @@
 ---
-title: "Runner installation behind firewalls"
+title: "Runner installation behind firewalls": Change title - remove installation
+working with Runner behind firw
 description: "Run Codefresh pipelines in your own secure infrastructure"
 group: installation
 redirect_from:
diff --git a/_docs/installation/gitops/argo-with-gitops-side-by-side.md b/_docs/installation/gitops/argo-with-gitops-side-by-side.md
@@ -30,72 +30,6 @@ There are three configuration changes to make _before_ installing GitOps on the
 2. [Synchronize Argo CD chart's minor versions]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/#gitops-with-argo-cd-synchronize-argo-cd-charts-minor-versions)
 3. [Set native Argo CD resource tracking to `label`]({{site.baseurl}}/docs/installation/gitops/hybrid-gitops-helm-installation/#gitops-with-argo-cd-set-native-argo-cd-resource-tracking-to-label) 
 
-<!--- ### Switch ownership of Argo project CRDs
-If you have Argo project CRDs on your cluster, Codefresh recommends either adopting the CRDs to switch ownership to the GitOps Runtime, or handling the CRDs outside the chart.  
-Allowing the GitOps Runtime to manage the CRDs also ensures that the CRDs are automatically upgraded whenever the Runtime is upgraded. 
-
-You have two options to adopt Argo project CRDs:
-
-#### (Recommended) Adopt the Argo project CRDs
-You can either adopt all CRDs which is the recommended option, or only Argo Rollout CRDs.
-
-**Option 1: Adopt _all_ CRDs (Recommended)**
-Adopting _all CRDs_ switches ownership for them to the Hybrid GitOps Runtime, allowing them to be managed by the GitOps Runtime chart. 
- 
-* Run this script _before_ installation:
-```
-curl https://raw.githubusercontent.com/codefresh-io/gitops-runtime-helm/main/scripts/adopt-crds.sh | bash -s <runtime-helm-release name> <runtime-namespace>
-```
-
-**Option 2: Adopt only Argo Rollout CRDs**
-You can also adopt only those CRDs that apply to Argo Rollouts. Adopting Argo Rollouts CRDs also switches ownership of the Rollout CRDs to the GitOps Runtime, and ensures that there is only one active Argo Rollouts controller active on the cluster with the GitOps Runtime. 
-
-* Run this script _before_ installation:
-```
-#!/bin/sh
-RELEASE=<runtime-helm-release-name>
-NAMESPACE=<runtime-namespace>
-kubectl label --overwrite crds $(kubectl get crd | grep argoproj.io | awk '{print $1}' | xargs) app.kubernetes.io/managed-by=Helm
-kubectl annotate --overwrite crds $(kubectl get crd | grep argoproj.io | awk '{print $1}' | xargs) meta.helm.sh/release-name=$RELEASE
-kubectl annotate --overwrite crds $(kubectl get crd | grep argoproj.io | awk '{print $1}' | xargs) meta.helm.sh/release-namespace=$NAMESPACE
-``` 
-
-#### Handle Argo project CRDs outside of the chart 
-Disable CRD installation under the relevant section for each of the Argo projects in the Helm chart:<br>
-  `--set <argo-project>.crds.install=false`<br>
-  where:<br>
-  `<argo-project>` is the Argo project component: `argo-cd`, `argo-workflows`, `argo-rollouts` and `argo-events`.
- 
-See [Argo's readme on Helm charts](https://github.com/argoproj/argo-helm/blob/main/README.md){:target="\_blank"}.  
-
-
-
-### Synchronize Argo CD chart's minor versions 
-To avoid potentially incompatible changes or mismatches, ensure that you use the same upstream chart version of Argo CD as that used by Codefresh.   
-
-1. Go to `https://github.com/codefresh-io/argo-helm/`.
-1. Navigate to `<upstream-chart-version>-<codefresh-version id>/charts/argo-cd/Chart.yaml`. For example, `https://github.com/codefresh-io/argo-helm/blob/argo-cd-5.38.1-1-cap-CR-18361/charts/argo-cd/Chart.yaml`.
-1. Find the Argo CD chart version that Codefresh uses in `dependencies.version`, as in this example: 
-
-{% include
-   image.html
-   lightbox="true"
-   file="/images/helm-side-by-side-argocd-version.png"
- url="/images/helm-side-by-side-argocd-version.png"
-  alt="Getting the Codefresh upstream chart version of Argo CD"
-  caption="Getting the Codefresh upstream chart version of Argo CD"
-  max-width="60%"
-%}
-
-
-
-### Set native Argo CD resource tracking to `label` 
-When you install GitOps on a cluster with an existing Argo CD installation, ensure that native Argo CD and GitOps Runtime's Argo CD use different methods to track resources. The same tracking method in both Argo CD instances can result in conflicts with the same application names or when tracking the same resource. 
-
-Verify that your native Argo CD instance uses `label` to track resources:
-* In the Argo CD namespace, make sure `argocd-cm.application.resourceTrackingMethod` is either not defined, in which case it defaults to `label`, or if defined, is set to `label`. 
-
--->
 
 ## Install Hybrid GitOps Runtime via Helm
 
diff --git a/_docs/installation/gitops/hybrid-gitops-helm-installation.md b/_docs/installation/gitops/hybrid-gitops-helm-installation.md
@@ -33,7 +33,7 @@ Choose the installation option that best aligns with your specific requirements
 * **First-time GitOps Runtime installation**   
   If this is your first time installing a GitOps Runtime in your Codefresh account, follow these steps:
 
-  * [Complete pre-requisites]((#prepare-for-gitops-runtime-installation)): Before starting the installation, complete pre-requisites, as described in Prepare for GitOps Runtime Installation.
+  * [Complete pre-requisites](#prepare-for-gitops-runtime-installation): Before starting the installation, complete pre-requisites, as described in Prepare for GitOps Runtime Installation.
   * [System requirements](#minimum-system-requirements): Check the minimum system requirements to ensure smooth installation.
   * [Step-by-step installation](#install-first-gitops-runtime-in-account): Follow our step-by-step guide to install the Hybrid GitOps Runtime from the Codefresh UI.
 
@@ -112,17 +112,43 @@ See [Argo's readme on Helm charts](https://github.com/argoproj/argo-helm/blob/ma
 ### GitOps with Argo CD: Synchronize Argo CD chart's minor versions 
 To avoid potentially incompatible changes or mismatches, ensure that the native Argo CD instance uses the same upstream version of Argo CD as that used by Codefresh.   
 
-1. Go to `https://github.com/codefresh-io/argo-helm/<upstream-chart-version>-<codefresh-version id>/charts/argo-cd/Chart.yaml`.  
-  For example, `https://github.com/codefresh-io/argo-helm/blob/argo-cd-5.38.1-1-cap-CR-18361/charts/argo-cd/Chart.yaml`.
-1. Find the Argo CD version in `app.version`, as in this example: 
+1. Get the Argo CD chart version used by Codefresh from the DEPENDENCIES either in ArtifactHub or from the gitops-runtime's `Chart.yaml` in Git: 
+  * [ArtifactHub](https://artifacthub.io/packages/helm/codefresh-gitops-runtime/gitops-runtime){:target="\_blank"}: 
+    {% include
+   image.html
+   lightbox="true"
+   file="/images/runtime/helm/helm-side-by-side-argocd-version-dependencies.png"
+ url="/images/runtime/helm/helm-side-by-side-argocd-version-dependencies.png"
+  alt="Getting the Codefresh chart version of Argo CD from Dependencies in ArtifactHub"
+  caption="Getting the Codefresh chart version of Argo CD from Dependencies in ArtifactHub"
+  max-width="60%"
+%}
+
+  * [`Chart.yaml`](https://github.com/codefresh-io/gitops-runtime-helm/blob/main/charts/gitops-runtime/Chart.yaml):
+
+    {% include
+   image.html
+   lightbox="true"
+   file="/images/runtime/helm/helm-side-by-side-argocd-version-dependencies.png"
+ url="/images/runtime/helm/helm-side-by-side-argocd-version-dependencies.png"
+  alt="Getting the Codefresh chart version of Argo CD from Dependencies in Chart.yaml"
+  caption="Getting the Codefresh chart version of Argo CD from Dependencies in Chart.yaml"
+  max-width="60%"
+%}
+
+1. Go to `https://github.com/codefresh-io/argo-helm/blob/argo-cd-<dependency-chart-version>/charts/argo-cd/Chart.yaml`  
+  where:
+  <dependency-chart-version> is the Codefresh Argo CD chart version you retrieved in step 1, for example, `5.38.1-1-cap-CR-18361`.
+
+1. Check the `appVersion` as in the example below.
 
 {% include
    image.html
    lightbox="true"
    file="/images/runtime/helm/helm-side-by-side-argocd-version.png"
  url="/images/runtime/helm/helm-side-by-side-argocd-version.png"
-  alt="Getting the Codefresh upstream chart version of Argo CD"
-  caption="Getting the Codefresh upstream chart version of Argo CD"
+  alt="Check versions"
+  caption="Check versions"
   max-width="60%"
 %}
 
@@ -244,7 +270,7 @@ You can define one of three different access modes:
 **GitOps with Argo CD**
 * `fullnameOverride` configuration for resource conflicts  
   Installing GitOps Runtime on the same cluster as Argo CD can cause conflicts when resources in both native and Codefresh's Argo CD instances have the same name or attempt to control the same objects.
-  Customizing `fullnameOverride` values for Argo CD and Argo Rollouts in the GitOps Runtime's `values` file prevents these conflicts.
+  Customizing `fullnameOverride` values for Argo CD and Argo Rollouts if installed in the GitOps Runtime's `values` file prevents these conflicts.
 
 * Resource tracking with `annotation`  
   Installing GitOps Runtime on the same cluster as Argo CD require that each Argo CD instance uses different methods to track resources. Using the same tracking method can result in conflicts when both instances have applications with the same names or when tracking the same resource. Setting the GitOps Runtime's Argo CD resource tracking to `annotation` prevents such conflicts. 
diff --git a/_posts/2023-08-30-aug-release-notes.md b/_posts/2023-08-30-aug-release-notes.md
@@ -0,0 +1,85 @@
+---
+title: "Release Notes: August 2023"
+description: "Release Notes for Codefresh Pipelines and GitOps"
+---
+
+## Features & enhancements
+
+### Pipelines: Enforce access to scopes for account
+With this feature, Codefresh admins gain enhanced control over the security of their pipelines by being able to restrict access to specific endpoint scopes.
+Scopes are defined at the account level, ensuring a consistent security baseline for all pipelines. These predefined scopes are inherited by every pipeline, which Codefresh admins can override for individual pipelines when necessary.  
+
+ {% include 
+image.html 
+lightbox="true" 
+file="/images/whats-new/aug23/rel-notes-aug23-pipeline-scopes-setting.png" 
+url="/images/whats-new/aug23/rel-notes-aug23-pipeline-scopes-setting.png" 
+alt="Configure scopes for pipeline" 
+caption="Configure scopes for pipeline" 
+max-width="60%" 
+%}
+
+For details, see [Configure scopes for pipelines]({{site.baseurl}}/docs/pipelines/configuration/pipeline-settings/#configure-pipeline-scopes).
+
+<br><br>
+
+### Pipelines: Initialization metric in Datadog
+Codefresh now reports an additional pipeline metric to Datadog. Reported metrics includes the duration of the initialization step for pipelines.
+
+<br><br>
+
+
+### GitOps: Application Groups in GitOps Apps dashboard
+
+Introducing a new view in the GitOps Apps dashboard, the Group view!  
+The Group view for GitOps applications is a simple and efficient way to streamline application deployment monitoring within your enterprise. 
+
+With App Groups, you can effortlessly focus on specific app deployments, as it consolidates deployment information for all applications within the group in the same view. This feature eliminates the need to navigate between the different applications for information on them.
+Tailor groupings according to the unique requirements of your organization and applications. 
+
+
+ {% include 
+image.html 
+lightbox="true" 
+file="/images/whats-new/aug23/rel-notes-aug23-app-group-page.png" 
+url="/images/whats-new/aug23/rel-notes-aug23-app-group-page.png" 
+alt="Application Groups in GitOps Apps dashboard" 
+caption="Application Groups in GitOps Apps dashboard" 
+max-width="60%" 
+%}
+
+Codefresh also adds the Group name as an annotation to the application manifest for easy organization and management. 
+
+For details, see [Application Groups for GitOps applications]({{site.baseurl}}/docs/deployments/gitops/gitops-app-groups/).
+
+
+
+
+
+
+
+## Bug fixes
+
+### General
+* Unable to sign in with SSO (Single Sign-On). 
+
+### Pipelines 
+* Prefix for Docker registries omitted when using a custom Docker registry as a Public Marketplace Registry. 
+* Pipeline trigger for BitBucket server does not fire on commit.
+* Pipeline resuming execution after approval shows previously executed steps as skipped in Codefresh UI.
+* Delay in start times for child pipelines triggered by parent pipeline including a large set of codefresh-run steps set to run in parallel.
+* Retrying a workflow displays duplicate metrics in Datadog.
+ 
+
+### GitOps 
+* Out of memory for Hosted GitOps Runtimes.
+* Clicking the **Current State** or the **Timeline** tab of an application opens the Home dashboard instead of the tabs.
+* Unable to connect to a Git provider when installing Hosted GitOps Runtimes.
+* Deleted GitOps applications continue to be displayed in the GitOps Apps dashboard.
+* (On-premises only) `DISABLED_CONCURRENT_SESSIONS` set to `true` results in `UNAUTHORIZED_ERROR token is not valid` error for graphql API call. 
+
+
+
+
+
+
diff --git a/images/runtime/helm/argo-cd-chart-version-artifacthub.png b/images/runtime/helm/argo-cd-chart-version-artifacthub.png
diff --git a/images/runtime/helm/argo-cd-chart-version-git.png b/images/runtime/helm/argo-cd-chart-version-git.png
