zalando / zalando/postgres-operator

Feature: include load balancer costs into cost calculation

Open
#1,829 0 comments 1 reaction 0 assignees View on GitHub

Nobody has claimed this yet.

enhancement
Dominant language
Go
Stars
5.2k
Forks
1.1k
Avg merge
2d 16h
Merged PRs (30d)
3

Description

  • Type of issue? feature request
  • Where do you run it - cloud or metal? Kubernetes or OpenShift? AWS K8s (the Zalando installation)
  • Which image of the operator are you using? (not sure how to find this out)
  • Are you running Postgres Operator in production? yes

The Operator UI on its "#/list" page shows a list of postgresql cluster managed by the operator, with an estimation of monthly costs.
pgui-list

These costs are calculated based on volume size (+ throughput/IOPs), memory + CPU requests and number of pods.

But there is another contribution to the total costs: The load balancers which are enabled by enableMasterLoadBalancer or enableReplicaLoadBalancer cost (with AWS's prices today) each 21.60 $/month, which (for smaller DBs like the ones in the screenshot) can easily exceed the other costs.

Request: Include the load balancer costs in the cost estimations shown in the #/list page.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start in ui/app/src/postgresqls.tag.pug around line 230, where the #/list cost estimate is calculated, and review the enableMasterLoadBalancer and enableReplicaLoadBalancer settings described in the administrator load-balancer documentation. Add the applicable AWS load-balancer costs to the displayed estimates and verify that clusters with either setting enabled show the additional monthly cost.

Written by the indexing model from the issue text.

Assessment

Tech stack
aws, kubernetes, postgresql, pug
Domain
cloud, databases, frontend
Issue type
Feature
Difficulty
3/5
Estimated time
1-2 days
Activity status
Stale
Clarity
Clearly specified
Newbie friendliness
52/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.