Currently with spread there is no way to deploy multiple RCs/pods within the same deployment. To enable this concept I would like to introduce a new Entity called Application and would function a lot like a docker-compose.yml file.
Applications can be attached with any Entity (potentially Application itself)
This will also cleanup some code in cli/deploy.go dealing with the case of only deploying objects from .k2e (if no RCs, Pods, or Containers are found). Instead of having special logic creating objects, input.Build() would return an Application with no attached entities and the objects from .k2e.
Currently with
spreadthere is no way to deploy multiple RCs/pods within the same deployment. To enable this concept I would like to introduce a new Entity called Application and would function a lot like adocker-compose.ymlfile.Applications can be attached with any Entity (potentially Application itself)
This will also cleanup some code in
cli/deploy.godealing with the case of only deploying objects from.k2e(if no RCs, Pods, or Containers are found). Instead of having special logic creating objects,input.Build()would return an Application with no attached entities and the objects from.k2e.