How Pods Are Counted for Billing

Understanding which pod conditions are billed and which are not, based on real-time Kubernetes event tracking.

How Billing Works

Per-Pod Time-Based Billing

Billing dihitung setiap 5 menit. Setiap pod di-charge berdasarkan waktu running sebenarnya.

charge_per_session = floor(elapsed_minutes) × (package_price_per_hour ÷ 60)

Untuk setiap session aktif, hitung elapsed sejak last_billed_at, bulatkan ke bawah, kalikan harga per menit.

BILLABLE BILLABLE_TERMINATING RESERVATION

Every 5 Minutes

Billing runs at minute 0, 5, 10, 15, 20, 25, 30, 35, 40, 45, 50, 55 (WIB).

1 Pod = 1 Session

Each tracked pod gets one open session. Duplicate sessions are prevented. Each session tracks last_billed_at.

Per-Minute Accuracy

Each session charges based on floor(elapsed_minutes). Short-lived pods are not overcharged.

Billable Pods

These pod conditions count toward your billing. Each open session contributes to the active billable pod count.

Pod Condition	Status	Reason	Why Billed
Running	BILLABLE	"container running"	Pod is actively consuming CPU and memory.
Running + Terminating	BILLABLE_TERMINATING	"terminating pod still running"	Pod has a deletion timestamp but containers are still running. Continues billing during grace period.
CrashLoopBackOff	RESERVATION	"CrashLoopBackOff — resource reserved"	Pod slot is reserved on the node even though the container is restarting.
OOMKilled	RESERVATION	"all containers terminated: OOMKilled"	Memory was consumed before the container was killed. Resource slot was in use. Auto-credit may apply.
Terminating + Containers Running	BILLABLE_TERMINATING	"termination in progress, containers still running"	Graceful shutdown in progress. Containers still serving until fully terminated.
Unknown Waiting State	RESERVATION	"unknown waiting state: ..."	Default to reservation for any unrecognized waiting state — safest assumption.

Not Billable

These pod conditions do not count toward billing. Sessions are closed or never created.

Pod Condition	Status	Reason	Why Free
PendingPodInitializingContainerCreating	FREE	"PodInitializing - initializing"	Pod is still booting or initializing. No persistent resource allocated yet.
ImagePullBackOff	FREE	"ImagePullBackOff - platform error"	Image cannot be pulled from registry — platform issue. Session closed. Auto-credit may apply.
InvalidImageName	FREE	"InvalidImageName - platform error"	Image name is invalid or inaccessible. Platform error. Session closed. Auto-credit may apply.
CreateContainerConfigError	FREE	"CreateContainerConfigError - platform error"	ConfigMap or Secret is missing or misconfigured. Session closed. Auto-credit may apply.
Unknown Phase	FREE	"unknown pod phase"	Pod phase cannot be determined — no session created.
Pod Deleted	FREE	"pod deleted"	Pod is gone from Kubernetes. Session is closed and no longer counted.
Terminating + Containers Stopped	FREE	"termination_completed"	Graceful shutdown finished. Session closed immediately.
No Application ID	FREE	session not created	Pod does not belong to any tracked application. No session created.

Session Lifecycle & Final Charge

Each pod gets one billing session. Every 5 minutes, session is charged based on elapsed time since last_billed_at. When pod is deleted, final charge applies remaining minutes (rounded up).

Event	Action	Status	Notes
Pod Added	Create Session (last_billed_at = started_at)	BILLABLE	Session created if no open session exists for this pod_uid
Every 5 min (Billing Tick)	Charge: floor(elapsed) × price_per_min, update last_billed_at	BILLABLE	Each active session charged for elapsed minutes since last_billed_at
CrashLoopBackOff	Restart count +1	RESERVATION	Session remains open — restart count accumulated, still billed
Platform Error	Session Closed (FREE), auto-credit applied	FREE	Session ends. Platform error credit issued to user balance.
Pod Deleted (HPA kill / manual)	Final charge: ceil(elapsed) × price_per_min, close session	FREE	Remaining minutes rounded up and charged. Session ended_at set to NOW.
Stale Session Cleanup	Force-close session (all statuses)	FREE	Runs every 15 min. Closes sessions >30 min old (including BILLABLE).

Per-Pod Time-Based Calculation

Periodic Billing (every 5 min)

elapsed = now - last_billed_at → billable_min = floor(elapsed_minutes)

Update last_billed_at

After each charge, last_billed_at = now so next tick only charges new elapsed time.

Final Charge (pod deleted)

elapsed = now - last_billed_at → final_min = ceil(elapsed_minutes) (bulatkan ke atas untuk coverage penuh)

Contoh Perhitungan per Skenario

Skenario	Periodic Tick (floor)	Final Charge (ceil)	Total
Pod hidup 3 mnt, lalu mati	0 (tidak ada tick)	ceil(3) = 3 mnt	3 menit
Pod hidup 3.7 mnt, lalu mati	floor(3.7) = 3 mnt	ceil(3.7) = 4 mnt	4 menit
Pod hidup 5 mnt pas, lalu mati	floor(5) = 5 mnt	ceil(0) = 0 mnt	5 menit
Pod hidup 8 mnt, lalu mati	floor(5) = 5 mnt	ceil(3) = 3 mnt	8 menit
Pod hidup 17.5 mnt, lalu mati	floor(5) × 3 = 15 mnt	ceil(2.5) = 3 mnt	18 menit

Kenapa floor + ceil? Floor di periodic tick memastikan pod tidak di-charge untuk menit awal sebelum tick pertama. Jika pod mati sebelum tick kedua, final charge dengan ceil mengambil semua sisa menit. Kombinasi ini memastikan tidak ada menit yang hilang meskipun pod mati di antara dua tick.

Quick Reference

$ Billable — Session Counted

RunningBILLABLE

Running + TerminatingBILLABLE_TERM.

CrashLoopBackOffRESERVATION

OOMKilledRESERVATION

Unknown WaitingRESERVATION

✕ Not Billable — Session Free

Pending / InitializingFREE

ImagePullBackOffFREE

InvalidImageNameFREE

ConfigErrorFREE

Pod Deleted / TerminatedFREE

Per-Pod Time-Based Billing

Setiap pod di-charge berdasarkan waktu running sebenarnya. Setiap 5 menit, elapsed sejak last_billed_at di-floor dan di-charge per menit. Saat pod dihapus, sisa waktu di-charge dengan ceil (bulatkan ke atas). Ini lebih akurat dan adil untuk user dan platform.