Summary
User inquires about the implications of setting
CONTAINER_ORCHESTRATOR_ENABLED=false, particularly regarding resource consumption and orchestration processes in Docker and Kubernetes setups.
Question
Hi!
Are there any practical downsides of setting CONTAINER_ORCHESTRATOR_ENABLED=false ?
The documentation explains that there is no separate process handling the orchestration but it does not explain why I should care.
Not having a separate orchestrator is the default in the docker compose setup but not in Kubernetes - again I didn’t find an explanation and it does not make sense to me intuitively 
I’d like to avoid unnecessary resource consumption and the current setup already eats a lot of resources.
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.