Owner: Architect:

Story (Required)

As a contributor, it would be good to investigate controller-runtime abstraction for watches as opposed to the client-go based informers.

Background (Required)

Currently, we are using informers. Ref. https://issues.redhat.com/browse/APPSVC-1322

Glossary

Out of scope

Performance testing.

In Scope

Investigate controller-runtime abstraction for watches.

Approach(Required)

1. Go through the SBO PR: https://github.com/redhat-developer/service-binding-operator/pull/1354/files
2. Go through controller-runtime docs

Demo requirements(Required)

The demo should show the functionality has not changed.

Dependencies

Edge Case

Acceptance Criteria

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