hyperledger-labs / hyperledger-labs/fabric-operator
adopt with customer k8s
Open
- Dominant language
- Go
- Stars
- 78
- Forks
- 47
- Avg merge
- 1h 24m
- Merged PRs (30d)
- 3
Description
@jkneubuh could you please double confirm if current operator project supports @davidkel's question in performance sandbox as David and I discussed at
https://github.com/hyperledger-labs/PerformanceSandBox/issues/63
Contributor guide
Research direction
Start by reading this issue and the linked PerformanceSandBox issue 63, then inspect the current fabric-operator project to compare its capabilities with David's question. Done means documenting whether the operator supports the requested customer Kubernetes performance-sandbox use case; the payload names no specific files or tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100