DinD support in Bevel to maintain support of internal chaincode under new Kubernetes versions

[icordoba]

Is your feature request related to a problem? Please describe.
Many Kubernetes cloud services, such as Microsoft AKS, have stopped supporting docker sock interconnection. This is required in the process of internal chaincode deployment, so as users upgrade the Kubernetes version, eventually, chaincode deploment stops working.
Hyperledger supports DinD (Docker in Docker) for this, so a configuration change is required in peer nodes

        - name: CORE_VM_ENDPOINT
#          value: unix:///host/var/run/docker.sock
          value: tcp://docker:2375

Adicionally, when tcp value is configured, a Docker special PV, PVC and Docker pod instance need to be deployed for chaincode to work (sample yaml files attached)

Describe the solution you'd like
Solution is included in this feature request but it needs to be automated via a configuration parameter in Bevel that allows user to determine if he wants unix or tcp connection to core Docker.

Describe alternatives you've considered
Only alternative is external chaincode, but has implications, specially in Fabric 2.2.2

Additional context
I have successfully changed bevel files to support this, but in a permanent fashion, so I need to manually deploy Docker yaml files. Also i can't now use older Kubernetes that support unix:/// CORE_VM_ENDPOINT value.

Docker DinD deployment files.zip

[ashii1994]

any solution for this , when we are using cluster 1.27 + how can we deploy chaincode in fabric @icordoba @atoulme @gezero @shemnon @ajsutton

[ex-aswath-edx]

hi when i try with this changes in my bevel , iam facing issue , @icordoba