Allow kubetest to define service accounts / secrets which can be applied to all generated test namespaces

[edaniszewski]

see: https://github.com/vapor-ware/kubetest/issues/174#issuecomment-604483366

Right now, this could be done by defining the manifest for it and ensuring it gets loaded for every test case, but if there are multiple cases, that could get a little annoying/cumbersome. It would be nice to be able to tell kubetest to use some manifests and apply them to all generated test namespaces for the test suite.

[ghost]

Hi @edaniszewski, I don't want to be that guy, but have you had a chance to take a look at this?

Many thanks, Gavin

[edaniszewski]

I haven't yet, but I did spend some time thinking a little bit about this and how it relates to the issue you mentioned in the linked comment thread. I think having this feature might help, but I don't think its necessarily required since there is still the notion of secrets in kubetest, so a pull secret could be specified manually. In any case, I believe you also said that the image you are using is public, so having secrets wouldn't really help in that case.. I'll comment more in the thread with some of my thoughts to keep it all in one place.