Exether opened a new issue, #6189:
URL: https://github.com/apache/camel-k/issues/6189
### What happened?
Hello all,
When an integration is updated, the integration pod is killed immediately at
the same time the new pod is created which leads to some downtime. In general
the downtime is short but if the new deployment has an issue it can be much
longer. In our context where availability is key, this is a big problem.
We expect the old pod to be deleted only when the new one is up and running.
I've searched the issues without success, reason why I'm posting a new one.
Let me know if this is duplicate.
I've found #5491 which might be related but I let you see.
This happened on 2.3.3 and 2.4.0 versions.
Having a workaround or even a 2.4.1 fix would be great.
Thanks
### Steps to reproduce
Let's use a basic-route.yaml (sorry I'm having trouble formatting this
correctly due to trailing dash, but any route will work):
`- route:
id: "basic-route"
from:
uri: "kamelet:timer-source"
parameters:
period: 20000
message: "Test 1"
steps:
- to:
uri:
"log:integrations.example.DependencyHandling?level=INFO&showHeaders=true&showBody=true&showProperties=true"`
First start the integration:
`> kamel run basic-route.yaml`
Wait for it to be running and then update it with something erroneous (here
a non existing configmap):
`> kamel run basic-route.yaml --config configmap:foo`
You will be left with only one integration pod unable to start
(ContainerCreating) when we expect to have one non-working pod plus the old one
still running.
Note that if you update the integration with something correct, the issue
still exists, there will be a small time during which there is not working pod.
The issue is also occurring with 2.3.3.
We have checked in 1.12.1, 2.2.0, 2.5.0 and this was working as expected.
### Relevant log output
```shell
```
### Camel K version
2.4.0
--
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: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
