Add support for enforce Recreate deployment strategy

[jancespivo]

What would you like to be added?

Add possibility to set Recreate deployment strategy even there is no Volume set. I believe compose without deploy:update_config has meaning there is no rolling update but rather recreate strategy (docker swarm default behavior).

Why is this needed?

I don't think https://github.com/kubernetes/kompose/issues/264#issuecomment-258667438 statement is right. Sometimes application expects it is run only in one instance. For example when consumes ordered stream from messaging and want to keep results in the same order. In this case it is needed to have set 1 replica and Recreate deployment strategy.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[jancespivo]

/remove-lifecycle stale