Owner: Architect:

Story (Required)

As an OCP administrator I will like to be able to deploy a Redis service endpoint definition (SED) via helm chart, so that workloads can bind to the SED using SBO.

Background (Required)

There is no consistent way to define a SED that can point to any Redis service and at the same time is bindable to any workload via SBO. By creating a charts the defines the SED we can easily deploy the SED and make it available for binding.

Glossary

SED: Service Endpoint Definition. See Epic for more details.

Out of scope

NA

In Scope

NA

Approach(Required)

We will create a chart following the design described in the epic targeting Redis

Dependencies

NA

Edge Case

NA

Acceptance Criteria

We have a chart representing a Redis SED in our SBO GitHub repo.
We have submitted the chart to our helm certification repo and all checks passed.
We can run helm test on the chart to verify the service is healthy
We have documented upstream and downstream how this chart can be used to deploy the SED and how it can be bound via SBO to a sample workload
We can demonstrate how this SED can be bound to a sample workload

INVEST Checklist

Dependencies identified
Blockers noted and expected delivery timelines set
Design is implementable
Acceptance criteria agreed upon
Story estimated

Legend

Unknown
Verified
Unsatisfied