CloudLens K8s / OpenShift Sizing Calculator

Production resource planning · auto-generates Helm & Sidecar deployment artifacts · v3.2

Cluster INFRA

Kubernetes Platform Sets runtime + overhead

Container Runtime

Worker Nodes

Pods / Node

Node vCPU

Node Memory (GB)

Traffic WORKLOAD

Deployment Mode

Aggregate Traffic / Node All pods on the node

Privileged Mode Required for DaemonSet on most platforms

Sensor Debug Logging

CloudLens Connection HELM

Helm Release Name

Namespace Where sensor runs

Chart Package .tgz file path

Image Repository

Image Tag

vController Host / IP vController endpoint

Project Key From vController UI

Custom Tags Optional, comma-separated k=v

Packet Type vController Connection Properties · what data the sensor sends

Per-Node DaemonSet Footprint

CPU Request—

CPU Limit—

Memory Request—

Memory Limit—

% of Node CPU—

% of Node Memory—

Cluster-Wide Totals

Total Sensor CPU Request—

Total Sensor CPU Limit—

Total Sensor Memory Request—

Total Sensor Memory Limit—

Total Mirrored Traffic—

Cluster Total Resources—

Helm Install Command DAEMONSET

Prefilled from your inputs. Copy-paste into your OpenShift / K8s cluster shell after logging in with oc login / kubectl config.

values.yaml (alternative to --set flags) HELM VALUES

Prefer version-controlled values.yaml over inline --set flags for production.

Sidecar Container Injection SIDECAR

Paste this cloudlens container block into your application Deployment/StatefulSet pod spec. There is no separate Helm chart for sidecar — CloudLens uses manual injection (shared pod netns).

OpenShift note: Sidecar mode requires an SCC granting SYS_RAWIO, SYS_ADMIN, NET_ADMIN capabilities, bound to your workload's ServiceAccount. SCC snippet is downloadable below.

Download Full Deployment Plan REPORT

One file with everything: scenario summary, sizing decision, all generated commands, deployment checklist. Share with your team or keep as a PoC record.

Tip: The markdown report renders in GitHub, GitLab, Slack, VS Code, Confluence, and Jira. For PDF, click Print / Save as PDF and choose "Save as PDF" in your browser's print dialog.

Reference: Sensor Sizing Tiers

Current selection highlighted. Values are pre-overhead (platform multiplier applied in outputs).

Traffic Tier	CPU Request	CPU Limit	Memory Request	Memory Limit	Typical Use Case
< 500 Mbps	250m	1 vCPU	256 MB	1 GB	Dev/test clusters
500 Mbps – 1 Gbps	500m	2 vCPU	512 MB	2 GB	Small production
1 – 3 Gbps	1 vCPU	4 vCPU	1 GB	4 GB	Standard production
3 – 5 Gbps	2 vCPU	6 vCPU	2 GB	6 GB	Mid-large production
5 – 10 Gbps	3 vCPU	8 vCPU	3 GB	8 GB	High-density / fintech
10 – 25 Gbps	4 vCPU	12 vCPU	6 GB	16 GB	Telco / hyperscale
25 – 40 Gbps	6 vCPU	16 vCPU	10 GB	24 GB	Telco core
40 – 100 Gbps	8 vCPU	24 vCPU	16 GB	32 GB	Hyperscale

Architecture Diagram Click to view (PNG · SVG · Markdown export available)