-
Notifications
You must be signed in to change notification settings - Fork 344
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.
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
re-deployment strategies #2256
Labels
area/core
Core features of the integration platform
kind/feature
New feature or request
status/never-stale
Comments
Right, we could also support the |
This issue has been automatically marked as stale due to 90 days of inactivity. |
lburgazzoli
added a commit
to lburgazzoli/apache-camel-k
that referenced
this issue
Aug 3, 2022
lburgazzoli
added a commit
to lburgazzoli/apache-camel-k
that referenced
this issue
Aug 3, 2022
lburgazzoli
added a commit
to lburgazzoli/apache-camel-k
that referenced
this issue
Aug 3, 2022
lburgazzoli
added a commit
to lburgazzoli/apache-camel-k
that referenced
this issue
Aug 3, 2022
lburgazzoli
added a commit
to lburgazzoli/apache-camel-k
that referenced
this issue
Aug 3, 2022
astefanutti
pushed a commit
that referenced
this issue
Aug 4, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Labels
area/core
Core features of the integration platform
kind/feature
New feature or request
status/never-stale
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.
The text was updated successfully, but these errors were encountered: