We need to extend end-to-end testing for CNA to get more confidence about the service stability and functionality.

Let's add a binding test for a CNA that does not have any binding dependencies

This would test
* credentials delivery
* cluster information collection

The test should remove the cluster information cached in the database after the
process so the the next run would trigger the collection again. (currently not
possible).

What we need for this?* a cluster what we can run agains

• a namespace on the cluster to deliver the secrets

The cluster needs to be accessible (perms to do the cluster-infor collection
and to create a syncset) by the account that runs the end-to-end test.

This should become a part of the test that we are now running from Jenkins every 15 minutes.

To complete the task

1. get all the prereqs from relevant people (app SRE)
2. extend the test
3. make sure it runs periodically