Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Ability to configure PodDisruptionBudget for integrations #1760

Closed
2 tasks
astefanutti opened this issue Oct 14, 2020 · 2 comments · Fixed by #1787
Closed
2 tasks

Ability to configure PodDisruptionBudget for integrations #1760

astefanutti opened this issue Oct 14, 2020 · 2 comments · Fixed by #1787
Assignees
@mmelko
Labels
area/managed-service Camel K as a Managed Service kind/feature New feature or request
Milestone
1.3.0

Comments

@astefanutti
Copy link
Member

astefanutti commented Oct 14, 2020 •
edited
Loading

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 or pod trait?
  • Make sure it is compatible with all the deployment strategies: Deployment, Knative Service and CronJob?
@astefanutti astefanutti added this to the 1.3.0 milestone Oct 14, 2020
@astefanutti astefanutti added the area/managed-service Camel K as a Managed Service label Oct 14, 2020
@mmelko
Copy link
Contributor

mmelko commented Oct 14, 2020

I will look at this.

@astefanutti astefanutti added the kind/feature New feature or request label Oct 14, 2020
@mmelko mmelko mentioned this issue Oct 26, 2020
Merged
@mmelko
Copy link
Contributor

mmelko commented Oct 26, 2020 •
edited
Loading

#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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mmelko mmelko

Labels
area/managed-service Camel K as a Managed Service kind/feature New feature or request
Projects
None yet
Milestone
1.3.0
Development

Successfully merging a pull request may close this issue.

Create PodDisruptionBudget for every integration mmelko/camel-k
2 participants
@astefanutti @mmelko