James Taylor
James Taylor
Currently the Fabric protobuf API can only be explored through the individual .proto files. It would be useful to publish a navigable API doc via GitHub pages. Additionally, with the...
It would be great to move from the current Go SDK to the new [Fabric Gateway](https://hyperledger.github.io/fabric-gateway/) client when possible.
See #119
MSP and peer ID annotations look like they might cause problems. Also potentially related to #88, can the object labels be improved to make management easier? [Valid label values](https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/): -...
Ideally the k8s pod should be terminated if the peer is terminated. This is related to #88 however it will not always be possible to add an owner reference.
The k8s builder currently creates pods to run chaincode directly, which leads to some problems managing and clearing up pods because the Fabric builder and launcher framework doesn't quite match...
Builds started failing on macos-latest when it updated to use macos-14 so they now specify macos-13 explicitly- see #116. There is probably less reason to build/test binaries on macos since...
Just misusing a GitHub issue as a quick project update for the [17th April Fabric call](https://wiki.hyperledger.org/display/fabric/Contributor+Meetings+2024)! ## State of the project Still active! Latest version is [0.12.0](https://github.com/hyperledger-labs/fabric-builder-k8s/releases/tag/v0.12.0), which fixes an...
It may be desirable to deploy different chaincode in different namespaces and, with #102, with different resource requests and limits. Currently the chaincode packages only contain information about what is...
The following is more than strictly necessary but a good starting point... ``` --- apiVersion: rbac.authorization.k8s.io/v1 kind: Role metadata: name: fabric-builder-k8s-role rules: - apiGroups: - "" - apps resources: -...