blocked by #703
Problem
DMOD should be able to orchestrate model executions and nodes via Kubernetes rather than Docker Swarm.
Expected Products
There should be a new implementation of the bases classes developed in #705 that operate by manipulating a local or remote kubernetes instance. Like with #706, there should be not outward obvious tells as part of the interface that hint that it is using kubernetes and the calling code should not need to do anything special.
Configuration classes and settings should be added to the code developed in #707 to enable this desired behavior.
Unit tests from #709 should be mirrored here for confirmation that DMOD may use the Docker orchestration backend OR the Kubernetes orchestration backend.
blocked by #703
Problem
DMOD should be able to orchestrate model executions and nodes via Kubernetes rather than Docker Swarm.
Expected Products
There should be a new implementation of the bases classes developed in #705 that operate by manipulating a local or remote kubernetes instance. Like with #706, there should be not outward obvious tells as part of the interface that hint that it is using kubernetes and the calling code should not need to do anything special.
Configuration classes and settings should be added to the code developed in #707 to enable this desired behavior.
Unit tests from #709 should be mirrored here for confirmation that DMOD may use the Docker orchestration backend OR the Kubernetes orchestration backend.