Fall back to regular execution if socket can't be opened

[stiller-leser]

SUMMARY

ISSUE TYPE

• Feature Idea

COMPONENT NAME

TURBO_MODE in cloud.common

ADDITIONAL INFORMATION

We are using the turbbo_mode together with an Ansible operator, written with the help of the operator-sdk. We have many 1000s of objects in our cluster, resulting in many parallel reconciliations and executions of the community.kubernetes collection.

Activating the turbo_mode helps to increase the performance drastically. After facing out of memory issues with the turbo_mode (see operator-framework/operator-sdk#5246 (comment)), we needed to make a couple of modifications already though:

• Only unlink if the socket is still present, otherwise processes will stay around, complaining that they can't unlink, ultimately resulting in OOM: Scaling the ansible operator for six custom resources with 1000s of objects operator-framework/operator-sdk#5246 (comment)
• Trying to connect to the socket (https://github.com/stiller-leser/cloud.common/blob/main/plugins/module_utils/turbo/common.py#L54) can fail with FileNotFoundError and ultimately a raise if the socket can't be created and / or is currently not existing (bbecause it was just termnated). Increasing the sleep (https://github.com/stiller-leser/cloud.common/blob/main/plugins/module_utils/turbo/common.py#L61) and increasing the TTL (https://github.com/stiller-leser/cloud.common/blob/main/plugins/module_utils/turbo/module.py#L142) via the environment variable helps somewhat

As we have many parallel reconciliations running, all calling the community.kubernetes collection (hence all resulting in the same socket name, resulting in the conflicts described above), it would be great to enable the possibility to instead of raising here https://github.com/stiller-leser/cloud.common/blob/main/plugins/module_utils/turbo/common.py#L60 having the code fall back to a regular module execution.

Best regards,
stiller-leser