Cluster secrets with empty project values, no longer scoped for all applications When you upgrade to Red Hat OpenShift GitOps v1.14, cluster secrets having an empty project value would no longer be treated as global secrets, scoped for all Applications and ApplicationSets. Previously, an Application or ApplicationSet would use any cluster secret matching the URL of the repoUrl field. From 1.14, we now check to see whether the project field of an application also matches the project field of the cluster secret. What this means is that if you have a cluster secret scoped to project-a, an application scoped to project-b can no longer make use of the secret. If you have a cluster secret that's intended to be used by applications in multiple projects, you need to unset the project field.