<p>By what I have seen so far, in a Hyperledger Fabric v1.4 network that has been deployed using Kubernetes, the chaincode container and the peer container co exist within the same pod. An example for the same can be found in this link <a href="https://medium.com/@oap.py/deploying-hyperledger-fabric-on-kubernetes-raft-consensus-685e3c4bb0ad" rel="nofollow noreferrer">https://medium.com/@oap.py/deploying-hyperledger-fabric-on-kubernetes-raft-consensus-685e3c4bb0ad</a> . Is it possible to have a deployment where the chaincode container and the peer container exist in two separate pods? If yes, how do I go about implementing this in Hyperledger Fabric v1.4? By my research, it is possible to do so in Hyperledger Fabric v2.1 using external chaincode launchers. However, I am restricted to Fabric v1.4 currently.</p>

<p>As you point out, Fabric v2.0 introduced <a href="https://hyperledger-fabric.readthedocs.io/en/release-2.0/cc_launcher.html" rel="nofollow noreferrer">external builders</a> which are specifically targeted to allow operators to choose how their chaincodes are built and executed.  With external builders it's certainly possible to trigger creation of a separate pod to launch the chaincode in.</p>

<p>Unfortunately, in Fabric v1.4.x there is a strong dependency on Docker.  You could potentially launch your docker daemon in a separate privileged pod, and securely authenticate to it via TLS, and launch your chaincodes there.  You can see the docker daemon connection configuration <a href="https://github.com/hyperledger/fabric/blob/v1.4.7/sampleconfig/core.yaml#L446-L481" rel="nofollow noreferrer">in the sample core.yaml</a>.</p>

<p>As a warning, I'm unaware of any users which are deploying peers connecting to a remote docker daemon.  I don't see any reason it should not work, but it's also not a well tested path. As external builders are available in more recent versions of Fabric, I don't expect a large amount of community support for novel docker configurations.</p>
