Locket should be independant from diego-api. Colocating them makes it less resilient and causes other instances to be incorrectly dependant on diego-api.
Description
Moving the locket from diego-api to it's own pod.
Motivation and Context
It solves issues with diego-api being only able to talk to the single locket co-located. It also allows for better separation of the two independant processes.
Fixes #1410
How Has This Been Tested?
Deployed in IBM hybrid testing environments.
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue)
[ ] New feature (non-breaking change which adds functionality)
[X] Breaking change (fix or feature that would cause existing functionality to change)
Checklist:
[ ] My code has security implications.
[X] My code follows the code style of this project.
[X] My change requires a change to the documentation.
[ ] I have updated the documentation accordingly.
Can you point me to the docs I would need to update and I can add those to the PR.
Locket should be independant from diego-api. Colocating them makes it less resilient and causes other instances to be incorrectly dependant on diego-api.
Description
Moving the locket from diego-api to it's own pod.
Motivation and Context
It solves issues with diego-api being only able to talk to the single locket co-located. It also allows for better separation of the two independant processes.
Fixes #1410
How Has This Been Tested?
Deployed in IBM hybrid testing environments.
Types of changes
Checklist:
Can you point me to the docs I would need to update and I can add those to the PR.