search

knative / serving

Kubernetes-based, scale-to-zero, request-driven compute
https://knative.dev/docs/serving/
Apache License 2.0
5.57k stars 1.16k forks source link

Knative Service down during an update #15545

Closed lsergio closed 1 month ago

lsergio commented 1 month ago

Ask your question here:

I have been using Camel-K for deploying my applications integrated with Knative. I noticed the following scenario:

Camel-K deploys a Knative Service, which creates a revision and its deployment. The service is ready and running. Then I update the application and the Knative Service is updated. At this time I expected Knative to create a new Revision and shift traffic to it when it's Ready. However, I see that the existing Revision is being updated, which causes the existing deployment to be destroyed and a new one to be created, causing some downtime. Is there some configuration that controls this behavior? I'm using knative serving 1.15. With Knative 1.12 I haven't noticed this behavior.

skonto commented 1 month ago

Hi @lsergio, maybe Camel-K is affecting the revision somehow. @matzew or @pierDipi may know more here. Are there any steps to reproduce it? What update did you make?

lsergio commented 1 month ago

I'll try and create an isolated test.

lsergio commented 1 month ago

@skonto @matzew @pierDipi After some more troubleshooting, I realized Camel-K is actually deleting the existing Knative Service and creating a new one. So Knative is working as expected. I'll close this one and investigate on the camel-k side. Thanks.