claudio4j commented on pull request #2577: URL: https://github.com/apache/camel-k/pull/2577#issuecomment-908467217
> I think we can take the opportunity and make this more general than just `secret`. We should use the `path` concept (ie `TLSCertificatePath`) that will read a generic path on the runtime integration. That path will be filled by a secret/configmap/file/volume ... by the user via `--resource` option. It may not help in this case, because by using `--resource` the certificate files are mounted in the integration pod, but the openshift route for the edge case is created from the operator pod, so the certificate file just doesn't exist in operator pod file system. -- 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
