When we deploy a workflow with the gitops profile that uses the knative deploymentModel, the outdated knative revisions are not being cleaned up.

When we deploy workflows that are linked with the knative eventing system, as part of the initialization procedure the K_SINK env variable is injected by the knative operator. That's part of the regular initialization. Additionally, when we use the knative deploymentModel, that injection produces a new knative serving revision, which is also part of the regular initialization.

However, when the injection is produced in revision N (without the K_SINK injected) to produce the revision N+1 (with the K_SINK injected), revision N remains in the system but is inoperable, since lacks of the K_SINK. This produces a negative impact since the initialization pod might remain trying to restart due to the K_SINK health check, etc.

So, considering that revision N is completely useless, we are basically removing it.