📢 Help Needed: Calling all Users/ Adopters to Contribute to Sizing Guide
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 11
- Forks
- 9
- Avg merge
- 5h 15m
- Merged PRs (30d)
- 10
Description
### Describe the bug
### Description
We've created a [Sizing Guide](https://github.com/microcks/community/blob/main/install/SIZING.md) for Microcks on Kubernetes and need YOUR real-world deployment data to make it accurate and comprehensive!
The guide helps users properly size their Microcks deployments based on expected usage patterns and resource requirements.
### What we need:
- Resource allocations (CPU/memory for Microcks, MongoDB, Keycloak)
- Performance observations under different loads
- Environment specifications and scaling experiences
The guide contains detailed instructions on how to contribute your deployment data. Help the community avoid resource issues and make better sizing decisions!
### Attach any resources that can help us understand the issue.
_No response_
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Read install/SIZING.md and follow its contribution instructions. Gather deployment resource allocations, environment details, scaling experiences, and performance observations for Microcks, MongoDB, and Keycloak. Done means the real-world data is added to the sizing guide in a useful, accurate form.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, mongodb
- Domain
- databases, documentation, infrastructure
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100