Please pay attention that all calculations presented on this page are relative and may differ from AWS CUR and Kubecost.
These calculations are valid for an environment that works full time (24 hours) and does not take into account possible shutdowns during the weekend or at night.
This documentation provides an estimation of costs associated with different namespace configurations in the Rancher system. Understanding the costs involved in namespace configurations is essential for effective resource management and budget planning. This estimation takes into account various factors such as replica count, memory allocation, and resource sharing.
Within this research, calculations were performed to determine the daily costs for various configurations of Rancher environments. The table below presents a list of configurations for the modules:
- Testing: Replicat count 1, Memory 100%
- Development: Replica count 1, Memory 75%
- Performance: Replica count 1, Memory 100% (currently identical to testing, but will be adjusted in the future for performance needs)
Additionally, these calculations take into account different configurations with embedded and shared resources such as OpenSearch, Kafka, and PostgreSQL.
In the table, the most commonly used configurations for each type are highlighted in bold.
The development configuration is suitable for small-scale deployments. It includes a single replica with a memory allocation of 75%. Shared resources, such as OpenSearch, Kafka, and embedded PostgreSQL, are utilized. The cost estimate for this configuration is ~15,32$ per day.