Overview:

We currently support configmap-based approach only. CRs provide some benefits (clear status and error) so consider implementing it.

Requirements:

A list of specific needs or objectives that an epic must deliver in order to be considered complete. Be sure to include nonfunctional requirements such as security, reliability, performance, maintainability, scalability, usability, etc. Initial completion during Refinement status.

• Existing "traits" object traits shall be honoured
• Common API users shall not be able to create objects with "declarative" trait"
• Expand the exisiting framework instead of creating a different mechanism

TBD

Technical Scope:

TBD

Out of Scope:

High-level list of items that are out of scope. Initial completion during Refinement status.

TBD

Outstanding Questions (Optional):

Include a list of refinement / architectural questions that may need to be answered before coding can begin. Initial completion during Refinement status.

TBD