You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by GitBox <gi...@apache.org> on 2021/02/01 13:57:05 UTC

[GitHub] [camel-k] nicolaferraro opened a new issue #1976: Make the Camel K operator more involved in the Knative SinkBinding flow

nicolaferraro opened a new issue #1976:
URL: https://github.com/apache/camel-k/issues/1976


   Currently the operator just delegates SinkBinding to apply changes to the deployment/ksvc/cronjob child resources of an integration. This may result in unexpected errors in deployments/pods when the binding happens late or has an error (because of env vars missing).
   
   It would be good if the operator could put the integration in a "waiting for binding" state (maybe the same used for service-binding, thanks to @johnpoth), then proceed only when the binding is done, to avoid temporary errors.
   
   To do this, we should look into sinkbinding to see if they have a way for external operators to intercept the flow (like service-binding does). Otherwise we may think to (contribute it, or) make the integration podSpecable, so that the SinkBinding is applied to the integration itself, not to the child resources.


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [camel-k] lburgazzoli commented on issue #1976: Make the Camel K operator more involved in the Knative SinkBinding flow

Posted by GitBox <gi...@apache.org>.
lburgazzoli commented on issue #1976:
URL: https://github.com/apache/camel-k/issues/1976#issuecomment-770932445


   I think we have talked about this in the past already and maybe a new "waiting" state could be useful in general i.e. we may pause an integration than needs a not yet available secret


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org



[GitHub] [camel-k] nicolaferraro commented on issue #1976: Make the Camel K operator more involved in the Knative SinkBinding flow

Posted by GitBox <gi...@apache.org>.
nicolaferraro commented on issue #1976:
URL: https://github.com/apache/camel-k/issues/1976#issuecomment-770934778


   > I think we have talked about this in the past already and maybe a new "waiting" state could be useful in general i.e. we may pause an integration than needs a not yet available secret
   
   Yeah, same waiting state and multiple conditions seems feasible.
   
   I think SinkBinding can only work on PodSpecable currently.


----------------------------------------------------------------
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.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org