Allow to pin specific MongoDB Agent version to be used
What is the problem that needs to be solved? In some rare situations where upgrade of Cloud Manager's MongoDB Agent to the latest version leads to Golang panic (or any other critical issue) there's no way for Cloud Manager user to rollback MongoDB Agent version in case if this environment is running in Kubernetes Operator. The script which launch MongoDB Agent is using the latest version from Cloud Manager Project, without any option to change it other then editing the script itself which is not possible in Kubernetes pod.
Why is it a problem? (the pain) If after Cloud Manager's MongoDB Agent upgrade there are some critical issues (constant Golang panic, etc.) the user will be stuck awaiting MongoDB to rollback MongoDB Agent version in required Cloud Manager Project.
Alexey
shared this idea
We're currently planning work to avoid pulling mongod and the agent from Ops Manager. This is expected to give the ability to manually control the version of the agent in use.