From c0483659afe75167b8ad1fe8b48bea44ffd063e8 Mon Sep 17 00:00:00 2001 From: mrjones <8253488+mrjones-plip@users.noreply.github.com> Date: Fri, 4 Oct 2024 12:38:44 -0700 Subject: [PATCH] chore(#1528): example for small k8s deployment (#1575) * Add example for small k8s deployment per #1528 * fix typos, streamline text * update cost table use 3 vs 4 workers, cheaper instances --- content/en/hosting/costs/_index.md | 21 +++++++++++++++++++++ 1 file changed, 21 insertions(+) diff --git a/content/en/hosting/costs/_index.md b/content/en/hosting/costs/_index.md index 5f5ef51ee..824465d9e 100644 --- a/content/en/hosting/costs/_index.md +++ b/content/en/hosting/costs/_index.md @@ -66,6 +66,27 @@ It should be noted that a [development environment]({{< relref "hosting/4.x/app- Running an easy to set up Docker based development environment (instead of Kubernetes) on a laptop is an acceptable practice: there is no expectation of high uptime for development instances. +## Small deployment example costs + +In order to get a better idea of fixed monthly costs, let's look at the smallest Kubernetes deployment per the [requirements docs]({{< relref "hosting/requirements" >}}). These estimates use Amazon's [EC2 pricing](https://aws.amazon.com/ec2/pricing/on-demand/) and [EBS pricing](https://aws.amazon.com/ebs/pricing/) in Paris (`eu-west2`) availability zone. Please note different [types of EC2 pricing](https://aws.amazon.com/compare/the-difference-between-on-demand-instances-and-reserved-instances/) may have different costs along with other cloud providers which will have different costs as well. + +### Initial monthly costs as of 2024 + +| Item | Cost | Count | Total/mo | Note | +|-----------------|----------|-----------|------------|-------------------------| +| EC2 t4g.small | $0.01/hr | 1 | $8 | Control-plane node | +| EC2 c6g.2xlarge | $0.32/hr | 3 | $692 | Worker nodes | +| EBS SSD (gp3) | $0.09/mo | 500 | $45 | 500GB of shared storage | +| | | | | | +| | | **TOTAL** | **745/mo** | | + +### On-going costs and growth + +When running a small instance, be sure to plan for future costs. Do not assume that costs will stay flat or go down. Assume they will go up. Areas where costs can increase are: +* Backups - As your CouchDB instance takes more and more room, backups will cost more and more to store. +* Storage - As with backups, if the 500GB of storage approaches being full, or upgrades require a burst of disk use, plan on adding more active storage. +* More users - offline and online CHT Core users increase the load on the system. Be prepared to either add more worker nodes or increase the size of existing worker nodes to add more CPU and RAM. As well, consider stronger CPUs which might have higher clock speeds, more cache and be more efficient. + ## What's included in the per user cost This document covers hosting cost and does not cover Total Cost of Ownership (TCO). Below is a list of what's included in the hosting casts above and what is excluded.