This PR continues the refactoring of the deployment manager.
All service metadata is now always stored in the DB. Additionally the data is still set as labels/annotations on the running containers/pods but these labels are no longer used to reconstruct the metadata when listing the services.
Only the deployment status and internal id is not stored directly in the DB but is instead always queried during the deployment list/get request and is added dynamically to the response.
This also allows services to be created in a stopped status. That feature can for example be helpful to always create a default workspace for each user in ML Lab but don't have it running by default.
This PR continues the refactoring of the deployment manager. All service metadata is now always stored in the DB. Additionally the data is still set as labels/annotations on the running containers/pods but these labels are no longer used to reconstruct the metadata when listing the services. Only the deployment status and internal id is not stored directly in the DB but is instead always queried during the deployment list/get request and is added dynamically to the response.
This also allows services to be created in a stopped status. That feature can for example be helpful to always create a default workspace for each user in ML Lab but don't have it running by default.