Not sure exactly how we accomplish this one, but here's the use case.
I am often in the situation of wanting to deploy an Operator from a remote git repository. This repo likely does not use applier, and likely has a deploy/ directory containing multiple manifests files required to deploy it.
For example:
[esauer 🎩︎namespace-configuration-operator] (master)$ ls -l deploy/
total 20
drwxrwxr-x. 2 esauer esauer 4096 Aug 26 17:11 crds
-rw-rw-r--. 1 esauer esauer 918 Aug 26 17:11 operator.yaml
-rw-rw-r--. 1 esauer esauer 617 Aug 26 17:11 role_binding.yaml
-rw-rw-r--. 1 esauer esauer 866 Aug 26 17:11 role.yaml
-rw-rw-r--. 1 esauer esauer 87 Aug 26 17:11 service_account.yaml
In order to deploy this using applier, I have to add all of this to my seed-hosts.yml:
This gets very verbose, especially when setting up an entire cluster where I am deploying multiple operators. It would be nice to have a more succinct way of doing this. One possibly way would be to find a syntax that would cause applier to clone the directory mentioned and oc apply -f repository/deploy/ it instead.
Not sure exactly how we accomplish this one, but here's the use case.
I am often in the situation of wanting to deploy an Operator from a remote git repository. This repo likely does not use applier, and likely has a
deploy/
directory containing multiple manifests files required to deploy it.For example:
In order to deploy this using applier, I have to add all of this to my seed-hosts.yml:
This gets very verbose, especially when setting up an entire cluster where I am deploying multiple operators. It would be nice to have a more succinct way of doing this. One possibly way would be to find a syntax that would cause applier to clone the directory mentioned and
oc apply -f repository/deploy/
it instead.