Add Kubernetes support to Cello

[YoungHypo]

Background

The current agent (src/agents/hyperledger-fabric) can only run Fabric nodes on Docker, and is tightly coupled to docker.sock and cello-net (see node/service.py, chaincode/service.py). Kubernetes only exists as documentation (docs/agents/fabric-operator.md) — there is no implementation.

Goal

Allow an organization's peer/orderer nodes to run in a Kubernetes cluster, so that when api-engine orchestrates them through the existing REST contract it does not need to be aware of whether the backend is Docker or K8s.

Acceptance

On kind / minikube, bring up a peer; api-engine queries its status as RUNNING through the same REST calls, and chaincode install/commit/invoke completes successfully.

[chaitanyakatore]

@YoungHypo are you working on this issue ? I would love to contribute to this

[kafeelraza]

Hi @YoungHypo,

I am interested in this Kubernetes support work. I understand this is a large feature, so instead of directly attempting the full implementation, I would like to start by studying the current Docker-based Fabric agent flow and preparing a small design/proposal for how a Kubernetes backend can fit behind the existing REST contract.

I can begin by mapping the current Docker-specific logic in node/service.py and chaincode/service.py, identifying which parts are tightly coupled to docker.sock/cello-net, and proposing the first small implementation step for kind/minikube support.

Would this be a useful starting point before implementation?