✨📖 Adding designs folder and sample template

[christopherhein]

Per the discussion in the controller-runtime this fixes #807 adding so that I can add the design document for #518

Signed-off-by: Chris Hein me@chrishein.com

[christopherhein]

/assign @vincepri

[christopherhein]

/assign @DirectXMan12

[DirectXMan12]

Let's not do the full KEP template. I'd like to see something closer to the KB template (in fact, I kinda just think we should copy it). IMO, at least for us, KEPs are too complicated, intimidating, and paperwork-heavy.

[DirectXMan12]

Might be worth having a "is this a breaking change" section for controller-runtime too.

What I'm looking for when I read a proposal is:

• What does it do?
• Is it breaking (and did we consider making it non-breaking), and how does it evolve in the future (additional options, dependency changes, etc, if relevant)?
• How do we teach this (see Rust RFCs) and how does an example look?

That's pretty much it in terms of structure. At least in my opinion, anything more than that just gets in the way of people actually doing things at this scale.

Key point from the KB design template:

we want enough information to evaluate the design, but not so much that you're
annoyed by the overall design process and decide to bake cookies instead.

We should copy the designs README from KB too (adjusting slightly as necessary).

[vincepri]

/lgtm

[DirectXMan12]

/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: christopherhein, DirectXMan12

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [DirectXMan12]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment