docs: [RFC] Add Unmanaged Launch Template Removal RFC

[jonathan-innis]

Fixes #N/A

Description

This PR adds a RFC design doc recommending that Karpenter drop the spec.launchTemplateName field from the new v1beta1/EC2NodeClass and provides the rationale behind the decision, including alternative options.

How was this change tested?

N/A

Does this change impact docs?

• Yes, PR includes docs updates
• Yes, issue opened: #
• No

By submitting this pull request, I confirm that my contribution is made under the terms of the Apache 2.0 license.

[netlify]

✅ Deploy Preview for karpenter-docs-prod canceled.

Name	Link
🔨 Latest commit	2d762e9
🔍 Latest deploy log	https://app.netlify.com/sites/karpenter-docs-prod/deploys/64ab285239b75e0008cf244d

[sftim]

If we want to support custom launch templates, I would add a whole new custom resource, eg AWSCustomNodeTemplate. For example, we could have that as beta-grade, tested, best-effort code and an alpha API version.

To highlight the alpha state, bump the alpha API version every n months and deprecate old-enough alpha APIs.

[jonathan-innis]

I would add a whole new custom resource

This is a really interesting idea. If we had enough users doing this, I could imagine us doing something like this. This at least draws the line better between the two concepts so that we don't have two api concepts that have different incompatibilities with each other that make it hard to reason about.

[github-actions]

This PR has been inactive for 14 days. StaleBot will close this stale PR after 14 more days of inactivity.