Skip to content

Add CI Check for CPU/Memory Usage Regression in DevWorkspace Operator #1476

@rohanKanojia

Description

@rohanKanojia

Description:

Introduce a CI check that compares the CPU and memory usage of the DevWorkspace Operator deployed from:

  • the current pull request, and
  • the main branch

The check should use the Kubernetes Metrics API to gather runtime resource usage (CPU and memory) of the operator pod(s). If the difference exceeds a defined threshold, the check should fail, signaling a potential resource regression.

Why This Matters:

  • Helps prevent performance regressions during development.
  • Enables early detection of issues such as memory leaks or CPU spikes introduced by PRs.

Acceptance Criteria:

  • A CI job deploys both the operator from the PR and the latest main branch.
  • Resource usage (CPU and memory) is collected using the Kubernetes Metrics API.
  • A configurable threshold is defined for acceptable CPU/memory deviation.
  • CI check fails if usage exceeds the allowed deviation.

Metadata

Metadata

Assignees

Labels

No labels
No labels

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions