You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Nov 11, 2024. It is now read-only.
Request: Relax the ArgoCD dependency check when running kam bootstrap so users are not forced to install openshift-gitops operator if ArgoCD CRDs are already installed on the cluster.
Currently, running kam bootstrap on a cluster without the openshift-gitops operator will fail the dependency check.
✗ Checking if ArgoCD is installed with the default configuration [1s] [Please install OpenShift GitOps Operator from OperatorHub]
The text was updated successfully, but these errors were encountered:
Thanks for adding this issue. Currently, Kam is tightly coupled with OpenShift GitOps and Pipelines operators. I agree it should be smart enough to look only for CRDs.
A similar issue was brought up regarding the dependency on the sealed secrets operator. By specifying the --insecure option, it effectively disables the check for that operator. We should revisit the idea of having kam dependent on operators. Kam is also dependent on the pipelines operator.
Request: Relax the ArgoCD dependency check when running
kam bootstrap
so users are not forced to installopenshift-gitops
operator if ArgoCD CRDs are already installed on the cluster.Currently, running
kam bootstrap
on a cluster without theopenshift-gitops
operator will fail the dependency check.✗ Checking if ArgoCD is installed with the default configuration [1s] [Please install OpenShift GitOps Operator from OperatorHub]
The text was updated successfully, but these errors were encountered: