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 2020/10/14 07:10:37 UTC

[GitHub] [camel-k] astefanutti opened a new issue #1760: Ability to configure PodDisruptionBudget for integrations

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


   To improve high-availability of integrations, the Camel K operator should provide the ability to create PodDisruptionBudget resources for integration pods:
   
   https://kubernetes.io/docs/tasks/run-application/configure-pdb/
   
   Open points:
   
   - [ ] Where should the PodDisruptionBudget configuration be exposed? Should it be exposed by a dedicated trait, or grouped into a more general _scheduling_ trait?
   - [ ] Make sure it is compatible with all the deployment strategies: Deployment, Knative Service and CronJob?
   


----------------------------------------------------------------
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] mmelko commented on issue #1760: Ability to configure PodDisruptionBudget for integrations

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


   #1787 This is what I have so far. PDB is created for every integration and deleted with integration. I decided to go with new trait for the PDB but I can refactor if necessary.
   
   I still need to create test for the trait and also I'm not sure if `IntegrationRunning` phase is the best here. 


----------------------------------------------------------------
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] astefanutti closed issue #1760: Ability to configure PodDisruptionBudget for integrations

Posted by GitBox <gi...@apache.org>.
astefanutti closed issue #1760:
URL: https://github.com/apache/camel-k/issues/1760


   


----------------------------------------------------------------
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] mmelko edited a comment on issue #1760: Ability to configure PodDisruptionBudget for integrations

Posted by GitBox <gi...@apache.org>.
mmelko edited a comment on issue #1760:
URL: https://github.com/apache/camel-k/issues/1760#issuecomment-716569184


   #1787 This is what I have so far. PDB is created for every integration and deleted with integration. I decided to go with new trait for the PDB but I can refactor if necessary.
   
   I still need to create test for the trait and also I'm not sure if `IntegrationRunning` phase is the best here. 
   
   Also I have to test it with other deployment strategies


----------------------------------------------------------------
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] mmelko commented on issue #1760: Ability to configure PodDisruptionBudget for integrations

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


   I will look at this.


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