Guidance Requested: Submitting an Operator That Requires Credentials To Run

[jonathanrainer]

Hi,

We're currently working on trying to submit an Operator to OperatorHub but we're running into some problems with the PR tests because our Operator requires access to a secret in order to perform any useful functionality. We'd be very willing to generate a secret for the purposes of submitting the Operator to OperatorHub and performing any tests required in the future but we wondered what the guidance was for a situation like this? Is there a way we can submit the secret to some kind of central repository? Or even better could we gain access to some kind of PR hook so we could generate the secret on the fly for the purposes of testing?

I've had a good search through the documentation from both OLM and OperatorHub and I can't see any guidance as to what to do in this situation, so any help would be much appreciated!

Thanks

[mantomas]

Hi, if the usage of secret is hard requirement and cannot be by-passed by adding dummy defaults, then there is option to skip the installation test (already used by some operators), but in that case the pipeline does not test much. If you don't find workaround within your code, then we can exclude the operator in the config (with the downside of skipping the install part of CI).