Owner: Architect:

Story (Required)

As a developer I will like my workloads with labels that match an SBO CR label selector to be bound even after the workloads are created after the SBO CR.

Background (Required)

Label Selector is a very flexible feature that allow a group of compute resources to be bound as a group. This will provide more value to SBO as it will simplify the service endpoint data projection for big applications that have many compute resources include custom compute resources. As long as developer label their compute resources and created the corresponding SBO CR with label selector as target for the workload. This will enable developer to even package the SBO CRs in their Helm Charts or Operators with the only variable being the target service CR they need to bind to.

Glossary

Out of scope

In Scope

Approach(Required)

Once the SBO CR is created with a label selector we can start watching for all compute resources with that match the label selector on the current namespace. Kubernetes allows for filtering by labels when we watch: https://kubernetes.io/docs/concepts/overview/working-with-objects/labels/#list-and-watch-filtering

Dependencies

Edge Case

Acceptance Criteria

All compute resources matching a specific label are bound.

INVEST Checklist

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

Legend

Unknown
Verified
Unsatisfied