openshift-gitops-getting-started
openshift-gitops-getting-started copied to clipboard
https://www.openshift.com/learn/topics/gitops/
App condition errors with a comparison error: ComparisonError rpc error: code = Unknown desc = Unable to resolve 'main' to a commit SHA This repo is missing the main branch...
Included instructions/resolution from the following issues thread to circumvent obstacles with syncing applications on ArgoCD. https://github.com/argoproj/argo-cd/issues/5886
This Service Account is needed in the namespace in Gitops 1.2.1. This allow the demo application to deploy with no issues.
Instruction says that after operator install the cluster name will be `openshift-gitops-cluster` when it is actually `argocd-cluster-cluster` [README page](https://github.com/siamaksade/openshift-gitops-getting-started) Using Red Hat OpenShift GitOps v1.0.0 operator
By default the app doesn't sync due to access control. I needed to manually update the spring-petclinic/spring-petclinic-role-binding so that the ServiceAccount name was "openshift-gitops-argocd-application-controller". The version in this git repo...
The Service Account name is wrong
Is there recommended settings for CRC? When I try the default, the CRC crashes.
I've only tested this on ROKS (Managed OpenShift) in IBM cloud. ArgoCD 2.5.4 installed via Red HatOpenShift GitOps 1.7.0 Operator When you install the OpenShift GitOps Operator, if on ROKS,...