📢 Help Needed: Contribute to Microcks Compatibility Matrix
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 comprehensive [Compatibility Matrix](https://github.com/microcks/community/blob/main/install/COMPATIBILITY-MATRIX.md) for Microcks and need YOUR real-world testing data to make it valuable for the entire community! The matrix documents which versions of dependencies (MongoDB, Kubernetes, Keycloak) and integrations (Jenkins, Backstage) work with different Microcks versions.
### Why Your Contribution Matters
- Help fellow users avoid deployment issues and version conflicts
- Share your expertise with the community
- Improve Microcks adoption by providing clear compatibility guidance
- Document real-world configurations that actually work in production
### How to Contribute
- Fork the [community repository](https://github.com/microcks/community)
- Edit the [COMPATIBILITY-MATRIX.md](https://github.com/microcks/community/blob/main/install/COMPATIBILITY-MATRIX.md) file
- Add your tested configuration to the appropriate table
- Create a pull request with your changes
### 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
Open install/COMPATIBILITY-MATRIX.md in the microcks/community repository and review its existing tables for MongoDB, Kubernetes, and integrations. Use a real-world tested configuration, add it to the appropriate table, and submit a pull request with the compatibility details.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, mongodb
- Domain
- devops, documentation, infrastructure
- Issue type
- Documentation
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100