Owner: Architect:

_<Architect is responsible for completing this section to define the
details of the story>_

Story (Required)

As an OpenShift user, If the SBO consumes more memory or CPU than a certain limits, the operator should crash instead of bringing down the entire cluster.

Background (Required)

The memory and cpu limits was commented out earlier:

https://github.com/redhat-developer/service-binding-operator/blob/e0ad01797ef9776348d34020c94fc2909c8e23f6/config/manager/manager.yaml#L49

Glossary

<List of new terms and definition used in this story>

Out of scope

<Defines what is not included in this story>

In Scope

<Defines what is included in this story>

Approach(Required)

After running the performance test in ideal conditions, figure out the memory and CPU limits and set them accordingly.

Demo requirements(Required)

Show crashing of the SBO operator after reaching the memory limit.

Dependencies

_<Describes what this story depends on. Dependent Stories and EPICs should
be linked to the story.>_

Edge Case

_<Describe edge cases to consider when implementing the story and defining
tests>_

Acceptance Criteria

• Set the "requests" memory value
• Set the "limit" memory value
• Set the "requests" CPU value
• Set the "limit" CPU value
• Minikube performance should be acceptable

Development:

QE:
Documentation: Yes/No (needs-docs|upstream-docs / no-doc)

Upstream: <Inputs/Requirement details: Concept/Procedure>/ Not
Applicable

Downstream: <Inputs/Requirement details: Concept/Procedure>/ Not
Applicable

Release Notes Type: <New Feature/Enhancement/Known Issue/Bug
fix/Breaking change/Deprecated Functionality/Technology Preview>

INVEST Checklist

Dependencies identified

Blockers noted and expected delivery timelines set

Design is implementable

Acceptance criteria agreed upon

Story estimated

v

Legend

Unknown

Verified

Unsatisfied