You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@camel.apache.org by "dmvolod (via GitHub)" <gi...@apache.org> on 2023/03/10 14:37:43 UTC

[GitHub] [camel-karavan] dmvolod opened a new issue, #681: Operator: Karavan CR strategy in the Kubernetes cluster (namespace)

dmvolod opened a new issue, #681:
URL: https://github.com/apache/camel-karavan/issues/681

   I don't really know is it by design or not, but now Karavan CR always create Deployment and other CRs with statically defined names "karavan" or simalar per namespace. Depends of the design, we should define:
   
   - Validation web-hook which will block to create more than single Karavan CR per namespace
   - If a single instance of Karavan deployment should be created per Kubernetes cluster, Karavan must be a cluster-wide CR
   - If we will be allow to create as number of Karavan instances per namespace as possible, corresponding dependent resources name prefix should be constructed, instead of hard-coded values.


-- 
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-unsubscribe@camel.apache.org.apache.org

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


[GitHub] [camel-karavan] mgubaidullin commented on issue #681: Operator: Karavan CR strategy in the Kubernetes cluster (namespace)

Posted by "mgubaidullin (via GitHub)" <gi...@apache.org>.
mgubaidullin commented on issue #681:
URL: https://github.com/apache/camel-karavan/issues/681#issuecomment-1739245892

   Karavan operator is deprecated in favour of installer


-- 
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-unsubscribe@camel.apache.org

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


[GitHub] [camel-karavan] mgubaidullin closed issue #681: Operator: Karavan CR strategy in the Kubernetes cluster (namespace)

Posted by "mgubaidullin (via GitHub)" <gi...@apache.org>.
mgubaidullin closed issue #681: Operator: Karavan CR strategy in the Kubernetes cluster (namespace)
URL: https://github.com/apache/camel-karavan/issues/681


-- 
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-unsubscribe@camel.apache.org

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


[GitHub] [camel-karavan] mgubaidullin commented on issue #681: Operator: Karavan CR strategy in the Kubernetes cluster (namespace)

Posted by "mgubaidullin (via GitHub)" <gi...@apache.org>.
mgubaidullin commented on issue #681:
URL: https://github.com/apache/camel-karavan/issues/681#issuecomment-1463944119

   By design:
   1. Only one Karavan deployment per namespace
   2. Unlimited number of Karavan deployments per cluster
   3. Deployment name `karavan` is hardcoded. 
   4. User can not create project with name `karavan` 


-- 
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-unsubscribe@camel.apache.org

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


[GitHub] [camel-karavan] dmvolod commented on issue #681: Operator: Karavan CR strategy in the Kubernetes cluster (namespace)

Posted by "dmvolod (via GitHub)" <gi...@apache.org>.
dmvolod commented on issue #681:
URL: https://github.com/apache/camel-karavan/issues/681#issuecomment-1463948993

   Ok, good point. Thanks for explanation.
   In this case, validation web-hook which will block to create more than single Karavan CR per namespace should be created.


-- 
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-unsubscribe@camel.apache.org

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