Be revision-friendly and do not use revisions by default on Knative profile

[nicolaferraro]

Service revisions are a nice thing as they allow to route traffic to different versions of the integration at the same time if needed.

But each time you do a redeploy a new revision (pod, running) is added and it scales down only after 5 minutes.
What's even worse is that if the deployment fails it's retried multiple times, generating at every cycle a new revision, blocking the whole cluster.

We should understand why a redeployment results in two different revisions if nothing changes.
We should use a different strategy by default, to avoid creating multiple pods if not required.

[nicolaferraro]

No longer a problem.

[nicolaferraro]

I'm not sure about the digest.. Let me verify..

[nicolaferraro]

Verified