default to the docker daemon in selector

[antoinemzs]

Proposed changes

• Defaulting to the docker daemon in the selector

Unify the defaults between opencti and openaev; favour the plain docker daemon as the more common deployment scenario

[antoinemzs]

@xfournet @richard-julien hi, we have spotted a possible discrepancy in the staging environments wrt the default engine and it looks like it would be easier for a newcomer to have the official image default to the plain docker daemon rather than kubernetes or portainer. Thanks!

[xfournet]

@xfournet @richard-julien hi, we have spotted a possible discrepancy in the staging environments wrt the default engine and it looks like it would be easier for a newcomer to have the official image default to the plain docker daemon rather than kubernetes or portainer. Thanks!

@antoinemzs

newcomers = new customer deploying xtm-composer or new dev on xtm-composer ?

What is the consequence of the change for already deployed xtm-composer ?

[antoinemzs]

As discussed, we set "kubernetes" by default for all products @xfournet

replies to the above questions:

newcomers = new customer deploying xtm-composer or new dev on xtm-composer ?

new deployements, i.e. someone using the official container for the first time

What is the consequence of the change for already deployed xtm-composer ?

breaking if the explicit config is not set, hence our latest conclusion.