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

re-deployment strategies #2256

Closed
lburgazzoli opened this issue May 3, 2021 · 2 comments · Fixed by #3511
Closed

re-deployment strategies #2256

lburgazzoli opened this issue May 3, 2021 · 2 comments · Fixed by #3511
Assignees
@astefanutti
Labels
area/core Core features of the integration platform kind/feature New feature or request status/never-stale

Comments

@lburgazzoli
Copy link
Contributor

As today integrations are re-deployed with a rolling deployment strategy but we need to make the re-deployment strategy configurable, i.e. we should be able to start the new pod/deployment only when the old one is completely shut down.
@astefanutti
Copy link
Member

Right, we could also support the Recreate strategy, that may be more appropriate, depending on the Integration connectivity or logic.

@astefanutti astefanutti added the area/core Core features of the integration platform label May 3, 2021
@astefanutti astefanutti self-assigned this May 3, 2021
@astefanutti astefanutti mentioned this issue Jun 7, 2021
Open
7 tasks
@github-actions
Copy link
Contributor

This issue has been automatically marked as stale due to 90 days of inactivity.
It will be closed if no further activity occurs within 15 days.
If you think that’s incorrect or the issue should never stale, please simply write any comment.
Thanks for your contributions!

@lburgazzoli lburgazzoli added status/never-stale kind/feature New feature or request and removed status/stale labels Oct 21, 2021
lburgazzoli added a commit to lburgazzoli/apache-camel-k that referenced this issue Aug 3, 2022
@lburgazzoli
re-deployment strategies apache#2256
14a4c49
@lburgazzoli lburgazzoli mentioned this issue Aug 3, 2022
Merged
lburgazzoli added a commit to lburgazzoli/apache-camel-k that referenced this issue Aug 3, 2022
@lburgazzoli
re-deployment strategies apache#2256
9c951e0
lburgazzoli added a commit to lburgazzoli/apache-camel-k that referenced this issue Aug 3, 2022
@lburgazzoli
re-deployment strategies apache#2256
7f6fca8
lburgazzoli added a commit to lburgazzoli/apache-camel-k that referenced this issue Aug 3, 2022
@lburgazzoli
re-deployment strategies apache#2256
bdaa4fb
lburgazzoli added a commit to lburgazzoli/apache-camel-k that referenced this issue Aug 3, 2022
@lburgazzoli
re-deployment strategies apache#2256
21d3092
astefanutti pushed a commit that referenced this issue Aug 4, 2022
@lburgazzoli @astefanutti
re-deployment strategies #2256
7eee5bc
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@astefanutti astefanutti

Labels
area/core Core features of the integration platform kind/feature New feature or request status/never-stale
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

re-deployment strategies lburgazzoli/apache-camel-k
2 participants
@astefanutti @lburgazzoli