feat: Add instance profile generation for v1beta1/NodeClass

[jonathan-innis]

Fixes #N/A

Description

This change adds instance profile generation when specifying a role in the v1beta1/NodeClass. This will not change the ways that instance profiles can be specified with the v1alpha5/Provisioner.

Starting in v1beta1, you will be required to specify a role in your EC2NodeClass like

apiVersion: karpenter.k8s.aws/v1beta1
kind: EC2NodeClass
metadata:
  name: default
spec:
  role: KarpenterNodeRole-karpenter-test
...

Karpenter will provision an instance profile that uses this role and propagate that profile into the EC2NodeClass status

apiVersion: karpenter.k8s.aws/v1beta1
kind: EC2NodeClass
metadata:
  name: default
spec:
  role: KarpenterNodeRole-karpenter-test
...
status:
  instanceProfile: karpenter-test_1234567890123456789

To ensure that instances that are using this instance profile are able to safely terminate, we now enforce that any v1beta1/NodeClaim that is using the EC2NodeClass must be removed before the EC2NodeClass will remove the instance profile and terminate. You can view this through the eventing logic like

➜  karpenter git:(v1beta1-testing) k describe ec2nodeclasses default
...
Events:
  Type    Reason                        Age   From       Message
  ----    ------                        ----  ----       -------
  Normal  WaitingOnNodeClaimTermination  18s   karpenter  Waiting on NodeClaim termination for default-8l2tz, default-frz5j, default-bfwnx, default-kzwhq, default-jp8dn and 5 other(s)

How was this change tested?

make presubmit

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	edf76d8
🔍 Latest deploy log	https://app.netlify.com/sites/karpenter-docs-prod/deploys/650decf6edf7060008970e90

[njtran]

Looks good. I have some questions about how we're planning on managing these instance profiles now.