Allow excluding IoT CRDs during Ansible installation (fixes #5046)

[ctron]

Type of change

• Enhancement / new feature

Description

Checklist

• Update/write design documentation in ./documentation/design
• Write tests and make sure they pass
• Update documentation
• Check RBAC rights for Kubernetes / OpenShift roles
• Try your changes from Pod inside your Kubernetes and OpenShift cluster, not just locally
• Reference relevant issue(s) and close them after merging
• Update CHANGELOG.md

[k-wall]

@ctron tested locally and had to fix a couple of bugs. it would for me now.

[kornys]

right now this PR does not makes sense why we set defaults to enable iot?

[k-wall]

right now this PR does not makes sense why we set defaults to enable iot?

why would the default be to disable? If I install from yaml bundle or OLM, I get IoT. If I install from Ansible, I would expect the same. We've added the option so that users of Ansible can elect to disable. I don't think it should be the default.

[kornys]

@k-wall because ansible is used only by integratly I think, and for testing they use our defaults inventory files, so it will cause troubles I guess if we change old behavior

[k-wall]

@kornys - I'm just arguing against a change in the behaviour of of our release. Previous releases defaulted to install IoT, so we should not break that. If users such as Integrately need to disable the IoT install, they will have to create their own inventory - or pass additional options to the ansible-playbook command line to inject additional parameters. That doesn't seem burdensome or unreasonable to me.

[lulf]

Release-0.33 branch was renamed to master: Please re-create PR against master branch.