hyperledger-labs / hyperledger-labs/fabric-operator
missing steps for deployment in a self-provisioned K8s cluster
- Dominant language
- Go
- Stars
- 78
- Forks
- 47
- Avg merge
- 1h 24m
- Merged PRs (30d)
- 3
Description
Currently, the deployment steps documented work for local or managed-k8s on cloud.
What's missing is steps for chaincode deployment over self-provisioned K8s cluster with a custom private registry. For example, with AWS and ECR as a reference K8s architecture, we could demonstrate the same.
Contributor guide
Research direction
Start by reviewing the existing documentation for local and managed Kubernetes deployment, then identify where chaincode deployment steps belong. Add a self-provisioned Kubernetes path using a custom private registry, with AWS and ECR as the reference architecture. Done means a newcomer can follow the documented steps end to end.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes
- Domain
- cloud, devops, documentation
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100