Olivia Taylor-Barrick

Test harness should support asserting that a specific number of a resource exist when listing

1

**What would you like to be added**: In the test harness, you can match objects without specifying a name, for example: ``` apiVersion: v1 kind: Pod metadata: labels: app: nginx...

https://rimusz.net/tillerless-helm/

We should also create NetworkPolicies to restrict what can talk to tiller and flux APIs.

We should separate the namespaced and cluster Flux types into two types: a Flux and a ClusterFlux. This would enable deploying either scope of flux using one flux-operator.

It would be useful to forward events to multiple upstreams, for example, you might want to get notifications on slack, send them to the [fluxcloud-webhook-monitor](https://github.com/karrieretutor/fluxcloud-webhook-monitor), and Sentry.