Luis Sergio Faria Carneiro

After the new node is created, the Integration status changes to Ready = true. The impact on my side is that the Error triggers the wrong workflow on my monitoring...

In this specific case, I think the Deployment is correct by not reporting an error before the deadline expires. Per the [docs](https://kubernetes.io/docs/concepts/workloads/controllers/deployment/), the deployment status should change to ProgressDeadlineExceeded after...

I checked the [source code](https://github.com/apache/camel-k/blob/main/pkg/controller/integration/monitor_deployment.go#L49) and looks like the Deployment monitor is waiting for the progressdeadlineexceeded status to report an Integration error. It seems there's something else causing the Integration...

After reading [this method](https://github.com/apache/camel-k/blob/v2.2.0/pkg/controller/integration/monitor.go#L349), I figured out what is happening: While there's no available nodes, the integration pod status is Pending and it reports: ``` status: conditions: - lastProbeTime: null...

I see. Well, one suggestion I have is to check the Deployment status Progressing condition. It is true, keep checking the Pods, but do not check for the Unschedulable reason....

No, this actually happened with a plain k8s Integration: ``` apiVersion: camel.apache.org/v1 kind: Integration metadata: name: base64test spec: sources: - name: main.yaml content: |- - from: uri: "rest:get:/base64" steps: -...

Using knative-serving 1.18.1

Checking the PA shows: ``` apiVersion: autoscaling.internal.knative.dev/v1alpha1 kind: PodAutoscaler metadata: annotations: autoscaling.knative.dev/class: kpa.autoscaling.knative.dev autoscaling.knative.dev/metric: concurrency autoscaling.knative.dev/minScale: "1" serving.knative.dev/creator: system:serviceaccount:dvdfyi9127:camel-k-operator creationTimestamp: "2025-10-23T18:03:23Z" generation: 3 labels: app: deploy-e57863cc-e0ab-46ec-9126-eaf2b9ecf227-00002 camel.apache.org/integration: deploy-e57863cc-e0ab-46ec-9126-eaf2b9ecf227 serving.knative.dev/configuration: deploy-e57863cc-e0ab-46ec-9126-eaf2b9ecf227...

Hi @dprotaso. I have changed the log level to debug and attached the logs for a few execution minutes. [autoscaler.log](https://github.com/user-attachments/files/23391588/autoscaler.log) As this is a production environment, I cannot change Knative...

Hi @squakez . I see this was closed automatically as not planned. Should it be reopened?