argo-cd/docs/operator-manual/upgrading/2.13-2.14.md

v2.13 to 2.14

Avoid v2.14.0 manifests and use v2.14.1

The tagged v2.14.0 manifests contain a nonexistent Argo CD image. If you are using the Argo CD manifests as a remote base, use the v2.14.1 manifests instead.

Eg, https://github.com/argoproj/argo-cd/manifests/ha/cluster-install?ref=v2.14.1 or https://raw.githubusercontent.com/argoproj/argo-cd/v2.14.1/manifests/install.yaml

Upgraded Helm Version

Helm was upgraded to 3.16.2 and the skipSchemaValidation Flag was added to the CLI and Application CR.

Breaking Changes

Sanitized project API response

Due to security reasons (GHSA-786q-9hcg-v9ff), the project API response was sanitized to remove sensitive information. This includes credentials of project-scoped repositories and clusters.

Added Healthchecks

• platform.confluent.io/Connector
• addons.cluster.x-k8s.io/ClusterResourceSet
• numaflow.numaproj.io/InterStepBufferService
• numaflow.numaproj.io/MonoVertex
• numaflow.numaproj.io/Pipeline
• numaflow.numaproj.io/Vertex
• acid.zalan.do/Postgresql
• grafana.integreatly.org/Grafana
• grafana.integreatly.org/GrafanaDatasource
• k8s.keycloak.org/Keycloak
• solr.apache.org/SolrCloud
• gateway.solo.io/Gateway
• gateway.solo.io/MatchableHttpGateway
• gateway.solo.io/RouteOption
• gateway.solo.io/RouteTable
• gateway.solo.io/VirtualHostOption
• gateway.solo.io/VirtualService
• gloo.solo.io/Proxy
• gloo.solo.io/Settings
• gloo.solo.io/Upstream
• gloo.solo.io/UpstreamGroup