Openshift GitOps RN requires a few modifications:

• Argo agent:

• • argo agent format seems to be of a binary in the current RN
  • Recommendation: Change `argocd-agent` to "Argo CD Agent" wherever its mentioned
  • The component matrix mentions the version as 0.2, it should be changed to 0.2.1
• Add known issue section
  • We had a customer ticket after the release. It would be good to include it in the RN 
    • https://issues.redhat.com/browse/GITOPS-7424

    • There is currently a known issue with clusters in FIPS mode where SSH based git repository connections fail due to a non FIPS compliant algorithm being used for SSH connections. A fix for this issue is being actively worked on and will be made available with an upcoming 1.17.1 version.
      
      Error: The repository server pod fails with an error: "panic: curve25519: internal error: scalarBaseMult was not 32 bytes"
      
      Workaround: Use HTTPS based git repository connections instead on a FIPS enabled cluster.

• Change hyperlink
  • Overview of Argo Agent is redirected to https://argocd-agent.readthedocs.io/latest/
  • What we want the customers to look at would be https://argocd-agent.readthedocs.io/latest/getting-started/openshift/
  • Since this is empty, it would be good to change the link once https://github.com/argoproj-labs/argocd-agent/pull/482 is merged and the content shows up in /openshift path.
• Rollouts Topology view

• • We did not include the rollouts topology view in RN as it was dev preview. It makes sense to not have a detail page about t but IMO we should include it as a feature in DP so that customers are aware. The feature being mentioned in blog post but not in RN has caused a little confusion
• Breaking changes
  • Default resource.exclusions configurations - https://issues.redhat.com/browse/GITOPS-6890

• • • With ArgoCD 3.0, a default configuration for resource.exclusions has been added in the argocd-cm to exclude resources that are known to be created by controllers and not usually managed in Git. However, the v2 behaviour has been preserved, and users can continue to use the .spec.resourceExclusions settings in ArgoCD CR if required.
      

• • We still use label tracking but upstream uses annotation tracking as default - https://issues.redhat.com/browse/GITOPS-6888

    • With ArgoCD 3.0, The default behavior for tracking resources has changed to use annotation-based tracking instead of label-based tracking. However, in order to avoid breaking the existing setup that use label-based tracking, this is still the default with operator

• • Persisting health status in Application CR - https://issues.redhat.com/browse/GITOPS-7009 

    • With ArgoCD 3.0, resource health statuses are stored in Redis instead of the Application CR as it gives a slight performance improvement by avoiding updates to the Application CR. However as it can cause issues for third party tools such as Red Hat Advanced Cluster Manager (RHACM) that rely on this status, the operator will maintain the previous setting by default. This can be overridden if needed by setting .controller.resource.health.persist to false in .spec.extraCommandArgs in ArgoCD CR

RN: https://docs.redhat.com/en/documentation/red_hat_openshift_gitops/1.17/html/release_notes/gitops-release-notes#errata-updates-1-17-0_gitops-release-notes