initial commit argocd-bootstrap #3
Conversation
There was a problem hiding this comment.
A few requested changes. However, a similar pattern has emerged with both PR's thus far in this repository:
Registering an operator using the OLM is an asynchronous process and in many cases results in an error when attempting to apply a Subscription and an associated custom resource. One such solution is to separate the OLM components and the custom resource creation. A verification can occur to ensure the CRD was applied successfully using the following example:
until oc wait --for condition=established --timeout=60s crd/argocds.argoproj.io; do sleep 2; done
| example: basic | ||
| example.com/component: operators | ||
| example.com/project: argocd-bootstrap | ||
| name: example-argocd |
There was a problem hiding this comment.
namespace field should be specified
|
@sabre1041 I'd like to separate the handling of the operator race condition as a separate issue. #14 |
There was a problem hiding this comment.
@sabre1041 @etsauer I have updated the argocd configs to address the comments. This should be good to merge
| example: basic | ||
| example.com/component: operators | ||
| example.com/project: argocd-bootstrap | ||
| name: example-argocd |
Add a directory that contains a set of manifests to install the argocd-operator and argocd, with accompanying README. I would love to add a sample app to be managed by argocd in future work