Add Managed Kubernetes in CAPI proposal

[pydctw]

Co-authored-by: Richard Case [email protected]
Co-authored-by: Winnie Kwon [email protected]

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

[pydctw]

@richardcase, I experimented with having a proposed option and alternatives considered but it just doesn't read well for me.

I think it is because we already have existing implementations and proposing option 3 without mentioning option 1 or option 2 first makes it difficult to understand why we even considered option 1 or option 2 in the first place.

So I have decided to leave them as is but restructured the proposal a little bit

• Separated out Managed Node Groups for Worker Nodes section from Managed Kubernetes API Design Approaches and moved Recommendation section before Managed Node Groups for Worker Nodes as our Recommendation is more focused on Managed Kubernetes API Design Approaches.
• Reworded Other Consideration for CAPI section based on comments.

Let me know what you think. If you find a better way to structure the proposal, I am all for it.

I will squash the commit and open the PR to CAPI repo before tomorrow's office hr based on your feedback.

[richardcase]

I agree i think it makes sense to keep the structure as it is....i think it flows better.

[pydctw]

Thanks for the formatting and updates. It looks much better.
Squashing the commit and opening a PR in CAPI. Will update a link in CAPI office hr notes.

[pydctw]

Closing this one