Connecting to existing pods not created by Kubedock #175
Description
Could you clarify Kubedock's support for pre-existing resources? Specifically, can Kubedock be configured to manage Pods (containers) that were not started by Kubedock, or is its scope limited only to the containers it orchestrates? I did not see this in the documentation.
I have a scenario where some resources are started as part of a previous step in our pipeline, but I want to use Kubedock to run some commands directly on these containers as part of our integration tests. These containers are not started as part of the integration tests but were created earlier without going via Kubedock. However, they were created on the same namespace as the kubedock service. When I try to list all containers using the docker-java API, 0 containers are returned.