Skip to content
EncryptTechBD
Home Industries Our Work Blog Pricing About Contact Discuss Your Project
বাংলা (BN)
Cloud, DevOps & FinOps 6 min read

Kubernetes operational readiness cost in Bangladesh

What Kubernetes readiness really costs: infrastructure, platform time, upgrades, observability, a calculator and a budget worksheet for Bangladesh teams.

E
EncryptTechBD · 0 comments
Aerial view of data centre buildings in Ashburn
Photo: Theodore Christopher / Wikimedia Commons

The cluster bill is the easiest part of Kubernetes to measure and usually the smallest part of what readiness costs. The larger line is the engineering time that keeps upgrades, certificates, policies and on-call rotas from becoming incidents.

This guide builds a cost model for operational readiness rather than for a cluster. It is written for teams in Bangladesh running a small platform, often with one or two people who hold the knowledge.

What readiness is buying

Readiness means the platform can be upgraded, patched, observed and recovered by someone other than the person who built it. That is an operating capability, not a feature, so the cost includes documentation, training and on-call as well as infrastructure.

A team that buys a managed cluster and skips those lines has bought capacity, not readiness. The gap appears at the first certificate expiry or API deprecation.

Nine cost lines

  • Control plane and cluster fees. Whether managed or self-managed, there is a base cost per cluster and a limit on how many you can reasonably operate.
  • Worker capacity. Requested CPU and memory, autoscaling headroom and the difference between what is reserved and what is used.
  • Networking and egress. Load balancers, NAT, cross-zone traffic and data leaving the provider.
  • Storage. Persistent volumes, snapshots, backup copies and the cost of keeping them in a second location.
  • Observability. Metrics, logs, traces and the retention that makes an incident review possible.
  • Security. Image scanning, policy enforcement, secret management and vulnerability response.
  • Delivery tooling. CI runners, registries, deployment controllers and environment separation.
  • People. Platform engineering time, on-call, training and the review work that upgrades require.
  • Environments. Staging, preview and demo clusters that often run at production size because nobody resized them.

The total-cost formula

Annual cost = infrastructure + (platform engineering FTE share × loaded salary) + on-call + tooling + upgrade and security work + training + contingency

Use a loaded salary, including benefits and overhead, or the people line will look cheaper than it is. Platform engineering is usually a share of one or more people rather than a dedicated hire; estimate that share honestly, then check it against the upgrade and on-call calendar.

Contingency belongs in the model because Kubernetes changes. Minor releases arrive roughly every four months, and each can deprecate an API your manifests still use. A budget with no upgrade time is a budget for an outage instead.

A planning split you set yourself

Before you have actuals, allocate the first-year estimate across four buckets and force the total to stay fixed: infrastructure, people, tooling and training. A workable starting split for a small platform is roughly 40 percent infrastructure, 40 percent people, 15 percent tooling and 5 percent training. Treat those numbers as a planning device, not as market data, and replace them with your own actuals after two quarters.

Ten inputs for the calculator

Score each from 1 (simple) to 5 (complex):

  1. Clusters: one development cluster scores 1; production plus staging plus a second region scores 5.
  2. Workload types: stateless services score 1; stateful databases, queues and batch jobs score 5.
  3. Traffic profile: steady internal traffic scores 1; public peaks and seasonal campaigns score 5.
  4. Release frequency: monthly releases score 1; several deploys a day score 5.
  5. Compliance: no external requirement scores 1; payment or regulated data scores 5.
  6. Team size: a dedicated platform pair scores 1; one engineer with other duties scores 5.
  7. Managed or self-managed: managed control plane scores 1; self-managed with etcd responsibilities scores 5.
  8. Observability maturity: basic metrics scores 1; logs, traces, alerting and retention policies score 5.
  9. Disaster recovery: backup only scores 1; tested restore in a second location scores 5.
  10. Multi-tenancy: one team scores 1; many teams with quotas and network policies score 5.

Use the total to choose a shape: 10–18 suggests a managed cluster with a narrow workload; 19–28 a production baseline with upgrade and on-call routines; 29–38 a platform with policy, observability and recovery testing; 39–50 a formal platform team with multi-cluster operations.

Hidden costs that appear after month three

Upgrade work. Reading release notes, testing deprecated APIs and rolling nodes is recurring labour, not a one-off project. Put it on the calendar before it becomes urgent.

Certificate and secret rotation. Automation reduces the work but adds a component that must itself be monitored.

Log volume. A verbose application can generate more observability cost than compute. Agree retention by data class rather than keeping everything forever.

Idle capacity. Requests set high "to be safe" and autoscaling that never scales down leave paid capacity unused. Review requests against actual use monthly.

Environment drift. A staging cluster that mirrors production doubles the bill and is rarely needed at full size.

Bangladesh considerations

  • Latency to regional cloud regions matters for interactive applications; test from Dhaka and Chattogram rather than from a laptop on office fibre.
  • Cloud bills arrive in dollars, so finance needs a card, a forecast and a process for exchange-rate movement.
  • Specialist Kubernetes experience is scarce; the cost of hiring or retaining it can exceed the infrastructure line.
  • On-call should match local working hours and holidays, with an escalation path that does not depend on one person.
  • Bandwidth and power interruptions make a tested restore and a documented manual fallback more valuable than another dashboard.

Budget worksheet

Cost lineOne-offRecurringOwnerEvidence
Cluster and control planeSetupMonthlyPlatform leadProvider invoice
Worker capacity—MonthlyPlatform leadUtilisation report
Network and egressDesignMonthlyNetwork ownerTraffic report
ObservabilityInstrumentationMonthlySRE leadRetention policy
Security toolingPolicy designMonthlySecurity leadScan results
Upgrade work—Per releasePlatform leadUpgrade log
TrainingCourse or mentorAnnual refreshEngineering managerCompetency record
Restore testingDrill designQuarterlySRE leadRestore report

When readiness is the wrong purchase

If the workload is one application, a small team and predictable traffic, a managed container service or a well-run virtual machine may deliver the same outcome with less operational surface. Compare total cost of ownership, including the upgrade calendar and on-call, before choosing a platform. The cheaper option is the one the team can operate repeatedly, not the one with the better demo.

A 90-day readiness plan

Weeks 1–2: inventory clusters, workloads and owners; record current utilisation and upgrade history.

Weeks 3–4: define the production baseline: resource requests, probes, policies, backup and alert routing.

Weeks 5–8: close the largest gaps, run an upgrade rehearsal and test a restore into a separate environment.

Weeks 9–12: publish the runbook, agree on-call, set a monthly cost review and schedule the next upgrade window.

Metrics that keep the cost honest

Cost per workload and per environment, requested versus used capacity, upgrade lead time, node patch coverage, deployment frequency, change failure rate, restore test result and on-call pages per week. Review them together; a cheap cluster with frequent pages is not cheap.

Where this fits in our work

Kubernetes operations sit within Managed Technology & Cybersecurity, alongside managed infrastructure protection and monitoring. The pricing page explains how assessments and ongoing care are scoped. For the readiness levels this budget should reach, read the comparison of Kubernetes readiness levels.

Sources

Services that deliver this

Want this implemented properly?

Pricing →

Every engagement starts with a written scope. If a requirement is outside it, we quote it separately before starting.

Responses (0)

No comments yet. Add the first one below.

Leave a response

Your email address will not be published. Required fields are marked *.

Keep reading

More field notes