You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@camel.apache.org by "Claus Ibsen (JIRA)" <ji...@apache.org> on 2017/05/26 09:18:04 UTC
[jira] [Commented] (CAMEL-11331) camel-kubernetes - Add Kubernetes
based RoutePolicy
[ https://issues.apache.org/jira/browse/CAMEL-11331?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16026045#comment-16026045 ]
Claus Ibsen commented on CAMEL-11331:
-------------------------------------
Yeah I think it would be good to get that donated from fabric8 to camel-kubernetes so its here OOTB and we can maintain this more active than f8 does.
> camel-kubernetes - Add Kubernetes based RoutePolicy
> ---------------------------------------------------
>
> Key: CAMEL-11331
> URL: https://issues.apache.org/jira/browse/CAMEL-11331
> Project: Camel
> Issue Type: New Feature
> Components: camel-kubernetes
> Reporter: Nicola Ferraro
> Assignee: Nicola Ferraro
> Fix For: 2.20.0
>
>
> We should try to create a Camel route policy based on kubernetes resource locking, as done in: https://github.com/fabric8io/fabric8-ipaas/tree/master/camel-master (but also https://github.com/kubernetes/kubernetes/blob/master/pkg/client/leaderelection/leaderelection.go).
> The implementation inside Camel will provide a RoutePolicy instead of a "master" component.
> [~davsclaus] do you think we should ask the fabric8 team to donate it to camel? I think we can just implement our route-policy version based on its algorithm. The two modules will not have the same API at the end, so we will not provide a replacement for it...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)