johnpoth commented on pull request #2235: URL: https://github.com/apache/camel-k/pull/2235#issuecomment-877048235
Hi @arthurdm ! For now, the strategy is to rely on the Service Binding Operator (SBO) to construct the binding Secret. The Camel-k Operator then mounts the Secret referenced in the `ServiceBinding` CR into the operand's Pod and then Quarkus takes over to construct the relevant POJOs. As the spec is still evolving the above approach might evolve with it. Specification adopters are scarce so it's hard to say. We therefore test this using a mock service. The drawback of the above approach is that the SBO needs to be installed before Camel-k as we listen to `ServiceBinding` CR to know when the Secret has been correctly created. Another drawback is that the `ServiceBinding` CR is "shared" between two Operators. A benefit of the approach is that we only create the Pod once the binding Secret is created so there are no useless Pod restarts (which is AFAIK the traditional workflow of the SBO). Using the SBO as a library is definitely worth exploring! Hope this helps ! -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
