Help Needed: How to size Microcks on Kubernetes

[krishi-agrawal]

Describe the bug

Description

We need comprehensive documentation on properly sizing Microcks deployments on Kubernetes environments. This should help users make informed decisions about resource allocation and scaling for their Microcks instances based on expected usage patterns.

Motivation

Currently, users don't have clear guidance on:

• Resource requirements for different components (Microcks API/UI, MongoDB, Keycloak)
• How to scale based on number of mocks/services
• CPU/memory recommendations for different usage patterns
• Storage considerations

Proposed Solution

Create detailed documentation covering:

• Resource requirements by component (tables with CPU/memory/storage recommendations)
• Environment-specific recommendations
• Example Kubernetes configurations
• How to use the benchmarking tool to validate sizing

Additional Context

This should integrate with the benchmarking work already completed in this issue using real performance data to inform the sizing recommendations.

Attach any resources that can help us understand the issue.

No response

[krishi-agrawal]

Closing this as the issue is continued here: #86